~/nahom_mekonen.prd open to offers
v2026.2 · last edited today
Product Spec · Personal

Nahom Mekonen

Product manager. Two products I owned end to end, walked through the way I actually think about them: the problem, the calls, the numbers.

Status Open to offers
NowHead of Product, Kabba
LocationMinneapolis · remote ok
Pathassociate PM → head of product
Methodgo and see for myself
Biasshipping over guessing

I'm the Head of Product at Kabba Transport, a software company working to change public transit across emerging markets in Africa. I joined as employee number 3 and, over the past 5 years, have owned product across our rider, driver, and operator apps, growing it into a platform that has now completed over a million trips for 100+ of the region's biggest companies.

I did not take the obvious path to get here. Coming out of school I had offers from Fortune 500 companies, and they were good ones. I turned them down because I wanted to work on a genuinely hard problem I had grown up around, and I was willing to take the risk on a young African startup to do it. It is the best bet I have made. On the weekends I built LinQ, free software for student transport operators in Minnesota.

1M+
trips completed
100+
enterprise clients
3→50+
team since I joined
95%
client retention
1.0Case studies

Two products I owned end to end, each walked through the same frame: the problem, how I validated it, the options I cut, what shipped, the numbers, and what I would change. Context: Kabba is shared mass transit built as a subway on minibuses, with fixed routes and monthly subscriptions. We launched first in Addis Ababa, one of Africa's fastest growing cities, where millions commute every day on an informal minibus network that was never designed for them. It was the sharpest version of the problem we set out to solve, so it was the right place to prove the model.

Case study: Kabba for Business
B2B corporate tier · the deep dive
CS-01
role: Senior PM, product owner
shipped: 2023, live
team: 6 eng · ops · finance
outcome: core revenue line

How I turned employee commuting into Kabba's highest margin product. The full arc, the way I would walk a hiring manager through it: the problem, the research, the options I killed, what shipped, and what moved.

# 1 · the problem

I kept seeing the same pattern in our ridership data: clusters of riders leaving the same office parks at the same time, many reimbursed by their employer. Digging in, I found companies were quietly running their own staff transport, renting buses, hiring drivers, and eating the safety complaints and no-shows themselves. It was expensive, off-mission, and a liability nobody wanted to own.

So I went and asked. I sat with 30 HR and operations leaders across 20 companies. The line that reframed the product came from an HR director who told me, plainly: "I don't want to be in the transportation business. I want my people to show up on time and I want the risk off my desk." They were not buying vehicles. They were buying attendance and peace of mind.

They weren't buying transportation. They were buying attendance, and the liability off their desk.
# 2 · why it mattered to the business

B2C revenue swung with weather, fuel, and paydays. Corporate contracts were the opposite: recurring, predictable, and high margin, and every company that signed anchored a route with guaranteed daily riders, which made the B2C service on that route more reliable too. One sale improved two products. That is the kind of leverage worth chasing.

# 3 · the options, and the ones I cut
Decision record
chose
A subscription tier with guaranteed seats on the shared network: a company admin dashboard, per-employee monthly billing, and attendance reporting for HR.
over A
Per-ride corporate billing. Cut it: no budget predictability for HR, and it guaranteed no capacity at peak, the exact thing they were paying to stop worrying about.
over B
Dedicated white-label shuttles per client. Cut it: capital heavy, low margin, and it threw away the shared network that made us different from the bus rental they already hated.
the bet
Guaranteed seats on shared routes gave HR a predictable line item and gave us margin without buying a single new bus. I used RICE to sequence: admin dashboard and billing were must-haves, advanced analytics waited.
# 4 · what we shipped

I wrote the specs and worked daily with six engineers, the operations team on route capacity, and finance on billing, and I presented the tier directly to client HR leaders and to our own executive team. We shipped in three parts:

  • An HR admin dashboard to enroll employees, assign them to routes, and see who is riding, the visibility that replaced their spreadsheets and phone calls.
  • Guaranteed seats on fixed routes with monthly per-employee billing, so HR got one predictable invoice instead of managing a fleet.
  • Attendance and usage reporting that gave HR proof their people were getting to work, the outcome they actually cared about.
Kabba Transport vehicle
fig · Kabba on the road in Addis Ababa
# 5 · the impact

Piloted with one anchor client of about 200 employees, then rolled out over roughly 18 months to a core book of business.

1→100+
corporate clients
~35%
of company revenue
95%
client retention, YoY
#1
highest margin product
before
~18%
after
~4%
Employee late arrivals on enrolled routes, the metric HR judged us on.
before
~6 hrs/wk
after
under 1
HR time spent managing transport logistics per client.
Reflection · what I would change
I found this too late. The demand was sitting in our ridership data from early on. I ran B2B discovery in month 18, not month 2. Our highest margin product should have been a hypothesis I tested in the first quarter, not a pattern I stumbled into.
I under-instrumented the pilot. I had strong qualitative signal from HR but thin baseline numbers, so the before/after took longer to prove than it should have. Now I set the measurement before the pilot, not after.
Case study: LinQ
Student transportation · built solo, free
CS-02
role: solo, on weekends
shipped: live
cost to operators: free
market: Minnesota, North Carolina

A side project I could not put down, and proof I can take a product from a real problem to a shipped, adopted tool on my own. Small operators move thousands of kids in seven-seater vans on paper and phone calls. I built them the software the big yellow-bus vendors never bothered to.

# 1 · the problem

"Type 3" operators run seven-seater vans for school districts, and they are invisible to the software market: too small for the big yellow-bus vendors to bother with. So they run routes on spreadsheets, sticky notes, and phone calls. And parents have zero visibility, no idea where their child is between home and school. I saw it up close, operators in my own community, family included, drowning every morning.

# 2 · the research

I sat with about 12 operators and rode along on the morning run. The real job was not the "route optimization" the big tools sell. It was two smaller, sharper things: the dispatcher knowing exactly who is on which van right now, and the parent knowing their kid is safe. Everything else was noise on the one morning that mattered.

Parents called the office all morning asking one question: where is my kid? Nobody could answer it.
# 3 · the options, and the one I cut
Decision record
chose
Build only two things: the dispatcher's daily screen and a live map for parents.
over
Matching the big vendors' feature lists, billing, invoicing, compliance reporting.
the constraint
I had weekends and nothing else, so I cut everything that was not the job the morning revolved around. Operators adopted it anyway, because it did the one thing paper could not.
# 4 · what shipped
  • A dispatcher daily screen with drivers, routes, and student assignments on one view, replacing the spreadsheet and the sticky notes.
  • A live parent app showing the real-time location of the van carrying their child, the feature I cared about most.
  • Routing and dispatch for seven-seater fleets, the segment the big-bus software had ignored.
# 5 · the impact
0→10+
operators adopted
10K+
students routed
2
US states
live
parent tracking
before
~2 hrs
after
~20 min
Dispatcher time to build the morning's routes.
before
a morning of calls
after
near zero
"Where is my kid?" calls to the operator, once parents had the live map.

We can track a package across an ocean. A kid on the way to school should not be harder to find than that.

Reflection · what I would change
Free got adoption but capped the learning. Giving it away got operators in fast, but without a price signal I could not tell which features they truly valued. Next time I would charge a small amount early, not for money, but for the truth.
I built for the operators I could reach. Mostly my own network. I would run wider discovery before assuming their morning was every operator's morning.
NMNahomnote
I built this for operators in my own community, family included, running real businesses on paper. It meant a lot to make something useful for them.
comment · open
2.0How I work

Four habits under everything above. The domain keeps changing. These do not.

  • Live the problem before I build. Two weeks as a user beats two months guessing. I rode the minibuses and I sat with the dispatchers.
  • Find the real job. People rarely want the feature they name. They want the outcome underneath it, and that is what I design toward.
  • Ship small and let reality vote. A rough version in someone's hands teaches me more than a flawless spec ever has.
  • Measure what changes a decision. If a number will not change what we do next, I leave it alone.
# the toolkit
product
Roadmapping & prioritization (RICE), PRDs & user stories, discovery & user research, A/B testing, OKRs & metrics, Agile / Scrum.
leadership
Executive & stakeholder communication, cross functional leadership, team & vendor management, go to market, B2B and B2C strategy.
technical
SQL & Python, REST APIs & integrations, GPS & location data, routing & dispatch logic, systems thinking, mobile & web.
domains
Mass transit & mobility, student transportation, fleet & dispatch, logistics, payments, marketplaces, emerging markets.
Leadershipresolved
MLT Fellow. Selected for a competitive program for high potential leaders in business and technology.
comment · resolved
3.0What's next
Next milestone

The next problem is yours.

I want to give the next hard problem the same care I gave this one: close to the people who feel it, inside a team building something that matters. If that is your team, I would like to talk.

4.0Appendix

Education

B.S. Computer Science

Metro State University · Dean's List

Earlier

Wings Transportation · software engineer intern (2019 to 2021). Built routing and driver-assignment tools for a ~200 driver fleet. Where I learned how dispatch really works.

Recognition

Africa Startup of the Year, nominee · urban mobility

MLT Fellow · leadership in business and tech

Also built

Nahom's HQ, an AI ops dashboard with two Claude agents that run my weekly reporting. I like building the tools I wish existed.

GitHub →