What twelve years in automation taught Olayinka Omotara about finding the problem first, and why she is building a room for the women who need to hear it.
The executives wanted their email intake automated, and fast. The email platform was about to be migrated, so Olayinka Omotara started by walking them through a workbook she had built. You list the processes you want to automate and answer questions about each: how standardised it is, the volume, the business rules, how often it changes. The workbook scores each one and says whether it suits robotic process automation (RPA), AI or a hybrid of the two.
They had never seen anything like it. What she heard was “Olayinka is complicating something simple.”
She told them it couldn’t be done and that they should wait. Anything she built would be wasted effort, she says, because the process that would run on the new system hadn’t been defined yet. She told them about automations that took six months and one that took a year. The expectation has shifted, she says: “But now that everyone has AI, everyone assumes it should take a week.”
Olayinka has spent twelve years in intelligent automation and AI. Her clearest evidence is an ATM reconciliation project for a bank, where the automation now processes 900 ATMs in about 75 minutes. Today she mentors women who are moving into, or growing within, automation and AI, and she is building Built Different, a free community for women who are “building anyway”.
An Education Problem
That’s when she stopped seeing it as a client problem. “It’s an education problem,” she says. Automation, she says, is getting a computer to do faster what a person normally does, and that part is true. But you find the problem first, and you understand the people first, “because people drive adoption”.
“When you haven’t seen the process behind the process, it looks like complication.”
Olayinka Omotara, Founder, Built Different
Most people were never taught that, she says, and teaching it is what she is building now.
The same thinking shapes how she sees the tools on the market. There’s a tool for everything, she says, so organisations keep buying tools and then asking how they can solve their problem. “But what is the problem?” she asks. “We have manual processes” is, in her words, “too vague and too big”.
She has sat in vendor pitches and left the room thinking, “So am I supposed to take your tool? I don’t see how it solves my problem.” Across the many meetings she has been in, she has watched executives say yes to tools they don’t need, then pressure the team to make the tool solve a problem it was never meant for. That’s when the fire-fighting starts, she says, and the team ends up reshaping the tool to fit a problem nobody defined.
So she flips it. “List the problems first. Then look for the tool.” A vendor who is handed specific problems, she says, “has to answer them, instead of showing off features”.
The wider market describes a similar pattern. In June 2025, Gartner predicted that more than 40% of agentic AI projects will be cancelled by the end of 2027, citing escalating costs, unclear business value or inadequate risk controls.
The trouble, she says, is that a stuck leader often doesn’t know how to find the problem.
Six Questions Called STABLE
That’s why she built STABLE, six questions a leader can put to a process. Each letter is one of them. Standardised: is the process standardised? Throughput: how much volume is there? Access: do we have access to the data? Business rules: are they defined? Low change rate: how often does it change in a year? Exceptions: what happens when a case leaves the happy path? The workbook she showed the executives is built on it.
She once held off on an automation because the platform it ran on was about to change. “That is the L in STABLE.”
On exceptions, she is specific. An exception is “any case that can’t be completed by following the documented steps without someone making a judgement call.” Map the normal path, look at a month of real cases and count how many left it. As a guiding principle, if more than 30% fall outside the standard path, she stops and fixes the process before automating. “It’s not a law. At 35% it might still be fine.” It is, she says, “a way to choose which processes are worth automating”.
Sometimes, she says, the answer isn’t automation at all. It’s optimisation, or people doing their jobs properly.
“If you automate chaos, you get faster chaos.”
Olayinka, Founder, Built Different
For the part about people, she points to one project.
The ATM Reconciliation Project
It was an ATM reconciliation project early in her automation career, around 2017 or 2018. The team knew the problem from the start. Reconciliation was slow, and it needed to be fast. But automation was new to her team and to the client, and they began with the tool: “this is what we’re going to build.”
Then the client’s people realised automation was coming through the door, and the project “started to be quietly sabotaged”. So her team changed the approach and made it about them. They met with the client’s team lead and showed him what he would gain: no Saturdays at work, no late nights, no hours in spreadsheets.
Once they made that shift, she says, her team had a champion. He gave them the background to the process and every exception case. He collected the rules from everyone on his own team and made sure it all worked. It still took time, with a lot of back and forth. “But because of him, it succeeded.”
The manual process was measured at 2.5 hours per branch. The bot runs at 5 seconds per terminal, and they could process 900 ATMs in about 75 minutes. The bank publicly announced its move into robotic process automation in 2018. As far as she knows, it’s still running, “probably at a much faster scale now”. It is the project that taught her that the tool is the easy part. “The people decide whether it lives.”
She was doing it without a mentor.
No Mentor, No Map
When she began her career, she says, she wanted someone who could tell her what came next. She didn’t have that, and nobody around her even understood what she was doing. The software robotics team was something most people had never heard of, and it was “an emotional roller coaster”. “I had no mentor. I Googled my way into everything,” she wrote in a recent post.
Her path ran from business analyst to project manager to developer to leading an automation practice, across Nigeria, the UK and Canada, including a Centre of Excellence built with a team of ten. She was, as she puts it on her profile, “often the only woman in the room, and the only Black woman at the table”.
Years later, after she moved to Canada and had more experience, she realised other people were in her shoes. They book calls with her, and most don’t ask about automation. They ask how she got here, how she landed the role, how they can grow into leadership.
She decided to build the room she never had.
Built Different
Built Different is that room, “where people can reach me easily and then guide others in turn,” she says. She started it for women in automation, but it grew bigger than that. “It’s for any woman who is building anyway.”
She names three turns that led to it. The first was seeing that this is an education problem: people didn’t understand automation, so they were afraid of it. The second was never having a mentor. The third was deciding to stop being a perfectionist.
“I’m a planner and a strategist, and that means I plan so much that nothing gets done,” she says. She was waiting for the perfect moment and the perfect conditions, with everything lined up. Then she decided it was time for action: “Let me start with what I have and go from there.” In a recent post she wrote: “I don’t have every answer yet, and I’m a little scared. But step one makes step two clearer, and I’d rather take it with you in the room.”
People assume she was born this way, she says. She wasn’t. She used to tell leaders, “You’re trying to go from 0 to 100 without passing through the numbers in between.” You start at 0, then 1, then 2.
“You’re not born this way. You build it, brick by brick.”
Olayinka, Founder, Built Different
That’s why it’s called Built Different, she says. And for her, it is more than titles.
Outside the Titles
Of the woman she hopes will read this, she says: “It is more than titles for me. It is understanding who she is outside the titles.” The person who shaped how Olayinka works is her husband.
He taught her resilience, consistency and belief, she says, and how to act when you truly believe in something. “Watching him changed how I work.” One thing he said has stayed with her: “Everything is working for you.”
“I believe in putting your money where your mouth is,” she says. “I believe I’m ordained to teach, and that I’ve been given a gift for being multifaceted.”
She is a fitness enthusiast and an artist. She works out because it helps her mind and keeps her strong and consistent. She draws mandalas because it calms her. Drawing is therapeutic, she says, the way writing in her journals used to be, and it replaced the journaling.
She named her art brand Dala, from the word mandala. It is where she puts her art on wearable pieces, starting with phone cases, and Dala has just signed with a marketing agency to take the brand further. “It’s an extension of the artistic side of me.”
Dala is one part of what she is building now.
Where Olayinka Is Now
The woman Olayinka most wants this article to reach has between 0 and 8 years in her field. She is good at her work and unsure about the next step. Olayinka hopes she will send it to a friend and say, “This is exactly what I needed to hear.” “I can relate to everything.”
Built Different is free to join, and you don’t have to be in tech. Sign-up is a two-minute form. Olayinka holds office hours for 30 minutes on Monday, Wednesday and Friday, 12:00 to 12:30 pm ET. “No idea is too silly,” she wrote, and the conversations are practical: updating a profile, planning a career switch, then step one, step two, step three. She asks one thing in return. “The room can’t do the work for you, so you’ll need to show up consistently.”
In her mentoring she works with women on career direction, on tailoring a profile and CV to the role they want, and on showing up with confidence in the room. For anyone who wants to talk first, she offers a free 15-minute conversation about where they are and where they want to go, in automation, AI or beyond. For leaders, she is turning STABLE into a guide, Find the Problem Before the Tool, so they can run the questions on their own processes.
The sentence she wants readers to take away is her own: “Anything is possible, but only one step at a time. Step one comes before step two.”
The Olayinka Omotara Playbook: Find the Problem First
1. Find the problem before the tool. List the problems first, then look for the tool.
2. Hand the vendor specific problems. “We have manual processes” is too vague and too big, so break it down until a vendor has to answer it.
3. Count the exceptions. Map the normal path, look at a month of real cases and count how many left it. Above 30%, stop and fix the process first, as a guiding principle and not a law.
4. Make it about the people. On the ATM project, no Saturdays at work, no late nights and no hours in spreadsheets turned the client’s team lead into the champion.
5. Start with what you have. Step one makes step two clearer.
From the Diary of Olayinka Omotara
Olayinka Omotara is a Canada-based automation and AI career mentor and the founder of Built Different.
| Role | Founder, Built Different and Dala by OlayinkaAutomation and AI Career Mentor |
| Based in | Canada |
| Also | Creator of the STABLE framework |
“Built. Not born.”
Editor’s Note
Executives Diary writes about Olayinka Omotara because she explains why automation projects stall on process and people before they stall on technology. Her account of an ATM reconciliation project for a bank puts specific figures behind that argument, and her STABLE questions give leaders a way to test a process before they buy a tool. She is also building Built Different, a free community she describes as the room she never had. The magazine presents her story as she tells it, in her own words.
Executives Diary, Editorial


