Product Leadership · Design Leadership · Baemingo
Leading product development for a scaling restaurant platform
Baemingo was preparing to grow to many more restaurants. The platform already had several products, from the point of sale to the ordering app and back office, but technical bugs, UX debt and reliance on internal help made it difficult for new restaurants to get started.
As Product Manager, I owned the roadmap across the platform. With four development teams, I needed to balance making existing products more reliable, improving the user experience and opening up opportunities for growth.
I led discovery and prioritisation, guided two consultant product designers and helped development teams move from detailed tasks to impact goals they owned. I also worked hands-on designing self-service onboarding and the menu builder.
The work brought a shared direction for product development, new and improved solutions across the platform, and a way of working that connected user needs, business goals and team ownership.
- My role
- Product Manager | Product Discovery & Development Leadership
- Year
- 2021–2022
- Teams
- Developers in four development teams, and two consultant product designers whose work I led
- Product leadership
- The roadmap, prioritisation and discovery for the cross-functional product teams
- People & process
- The design and development process, from discovery to launch and measuring the results, and one-to-ones with the two consultant product designers. The CTO was line manager for the developers.
- Discovery & design
- New initiatives I designed myself, from discovery and design to tests and development-ready design: the self-service onboarding and the menu builder
- How we worked
- No product owners: each development team owned its backlog together, and I drove the roadmap priorities by impact
- Industry
- Restaurant tech, B2B SaaS and fintech
- Products
- The POS for the till, the table, app orders and self-service, and the POS back office
- Company
- Baemingo
- Business model
- Subscriptions and payment transactions
The short version
The problem
Baemingo wanted to scale, but its products had technical bugs and UX debt while new restaurants relied on sales and internal teams to get started. Several products and user groups competed for the same development capacity. We needed to improve what restaurants already used while making room for new solutions.
My contribution
I owned the roadmap, prioritisation and discovery across the platform, aligned direction with the steering group and coordinated work across four development teams. I guided two consultant product designers, protected time for research and user testing, and helped teams work towards impact goals rather than prescribed solutions. I also designed the self-service onboarding and menu builder from discovery and testing to development-ready designs.
The outcome
We delivered a new design system, redesigned journeys and solutions allowing restaurants to sign up, build menus, activate payments and get started with less reliance on internal help. Product development gained a shared roadmap, and teams took clearer ownership of how problems were solved. The KPIs in this case are targets, not measured outcomes.
When a restaurant platform needs to scale
Baemingo was entering a stage where its platform needed to support many more restaurants.
The point of sale was at its heart. Whether guests ordered at the counter, at a table, through a self-service kiosk or in an app, each order passed through the same POS platform. In back office, owners and managers handled menus, payments, venue details and sales reporting.
The platform therefore had to work for people doing very different jobs: cashiers during the lunch rush, waiters at tables, diners ordering for themselves and owners managing the business behind the scenes.
- Online orderingGuests order and pay online and in the app
- Self-serviceGuests order at a self-service kiosk
- Table serviceWaiters take orders at the table
- Kitchen displaysOrders shown in the kitchen, and marked ready
- Venues
- Menus
- Payments
- Sales follow-up
Three needs competing for the same capacity
Existing products needed to become more reliable. Bugs affected tools restaurants and staff used every day.
The experience needed improvement. The products had accumulated UX debt. Interfaces and journeys needed to become more consistent and better suited to their users.
The platform needed to grow. New restaurants still depended on sales meetings and internal help, while demand for new features and products continued.
All three competed for the same development capacity.
My responsibility
I owned the roadmap and prioritised with the steering group. I worked with four development teams, whose developers reported to the CTO, and guided two consultant product designers.
My role was to set direction, clarify what mattered most and give teams the conditions to find good solutions. I had to bring together restaurant owners, staff, sales, customer success, support and business perspectives.
How could Baemingo grow without allowing technical problems, complicated journeys and administration to grow alongside it?
One roadmap balancing reliability, experience and growth
I brought product development together under a roadmap with three tracks. It made priorities visible and gave us a shared way to discuss what should happen now, later or not at all.
Three tracks in one plan
Make what we have reliable
Bugs affecting restaurants, staff and guests belonged on the roadmap, not outside new development.
Pay down the UX debt
We needed a new design system and improved interfaces and journeys suited to each product’s users.
Help more restaurants use the platform
We prioritised self-service and opportunities to strengthen the business through subscriptions and payment transactions.
A concrete prioritisation decision
We prioritised self-service onboarding and menus before payout activation.
Payments mattered to both restaurants and Baemingo’s business. But restaurants first needed an account and a menu. Without those, they couldn’t begin selling.
Payment activation was also a more complex initiative that could build on the onboarding guide. The sequence followed dependencies in the restaurant’s work, rather than whichever initiative appeared most commercially urgent at the time.
Themes in the restaurant’s own words
For the growth track, I used themes describing what restaurants wanted to achieve:
We can get started on our own.
We can build and change our menus ourselves.
We get paid from our first sale.
We can take every kind of payment at the till.
Each theme had an impact goal for restaurants and a business goal for Baemingo. I assessed user value, business potential and complexity in an impact matrix, and aligned the priorities with the steering group and teams.
A menu, for example, affected back office, POS, kiosk, app and online ordering. That made prioritisation across the platform essential.
Now
1“We can get started on our own”
Impact goalA new restaurant gets from sign-up to set-up on its own, without a sales meeting.
2“We can build and change our menus ourselves”
Impact goalRestaurants build and change their menus themselves, without contacting support.
Next
3“We get paid from our first sale”
Impact goalRestaurants activate payouts on their own, so they get paid from their first sale.
Later
4“We can take every kind of payment at the till”
Impact goalRestaurants take cash at the counter in the same system as card and app payments.
- 1“We can get started on our own”
- 2“We can build and change our menus ourselves”
- 3“We get paid from our first sale”
- 4“We can take every kind of payment at the till”
Targets that made direction measurable
We set targets including at least 70% of new restaurants getting started without a sales meeting, at least 90% of menu changes completed without support and 30% fewer support contacts per restaurant. We also set targets for stability, payments, user testing and business growth.
These were targets guiding the work, not reported outcomes.
The roadmap for all products
The roadmap covered every product we had: the POS at the till, at the table, for app orders and for self-service, and the POS back office. Each item belonged to one of the three tracks.
Scroll sideways to see the whole roadmap.
Two kinds of impact goals
Every theme had to do two things: help the restaurants reach their goals, and help Baemingo grow, through more subscriptions and more sales through Baemingo’s payments.
- 1“We can get started on our own”A new restaurant gets from sign-up to set-up on its own, without a sales meeting.SubscriptionsMore restaurants get started on their own, without a sales meeting.
- 2“We can build and change our menus ourselves”Restaurants build and change their menus themselves, without contacting support.Subscriptions and payment transactionsA restaurant can’t sell until its menu is in place.
- 3“We get paid from our first sale”Restaurants activate payouts on their own, so they get paid from their first sale.Payment transactionsNo transaction revenue until payouts are active.
- 4“We can take every kind of payment at the till”Restaurants take cash at the counter in the same system as card and app payments.SubscriptionsEvery sale in the same system, so the restaurant has no reason to keep a second till.
Targets per KPI
Each theme had KPIs with a target, so the teams knew what good looked like, and could see when a theme had done its job.
Stability and experience
Getting started
Menus
Payments
Growth for Baemingo
Letting restaurants’ needs guide the direction
To prioritise the right problems, we needed to understand where restaurants got stuck. I led discovery, bringing together research with key customers and users, knowledge from sales, customer success and support, and user testing of new solutions.
Three barriers to self-service
Restaurants couldn’t get started on their own
They needed a sales meeting and an internal team to set up the account.
Menus and sales channels were difficult to manage
Large product ranges took time to enter, and owners often needed help understanding how products, menus and channels fitted together.
Getting paid was unclear
Owners didn’t always understand why KYC details were required, how approval worked or what remained before payouts could begin.
The customer journey revealed dependencies
We mapped the journey from registration to first sale. The map showed what restaurants were trying to do and where they became dependent on sales, support or other internal teams.
It helped the steering group and developers see the problems as one connected experience rather than isolated support cases.
Scroll sideways to see the whole journey.
From insights to initiatives
The problems led to self-service registration and guided onboarding, a menu builder for different sales channels, and clearer payment activation explaining KYC, status and next steps. We also worked on sales-channel activation and cash payments at the till.
We tested journeys before development. A menu-builder test, for example, showed that restaurant owners wanted to create products first and build menus from them afterwards. That finding shaped the next design iteration.
Research helped us choose the right problems. Testing helped us find better ways to solve them.
- OpportunityGet started without waiting for usWhat we builtSelf-service onboarding
- OpportunityGet the menu right in every sales channelWhat we builtMenu builder
- OpportunityGet paid from the first saleWhat we builtPayment activation, with KYC explained
- OpportunitySell in more channelsWhat we builtSales channel activation
- OpportunityTake every kind of payment at the tillWhat we builtPay with cash
Different users, one design direction
Baemingo had several products, but the experience needed to feel connected. I made room for UX improvements on the roadmap and protected discovery, prototyping and testing as part of product development.
The two product designers designed the products and owned the design system. I guided direction, prioritisation and the conditions for quality.
One design system – different situations
Shared components didn’t mean every product should behave the same way. Cashiers needed speed, waiters needed to focus on guests, diners ordering on mobile wanted to get to their food, and owners needed to understand how to set up their business.
We therefore used principles we could test against real tasks.
- 1DiscoverUnderstand the needs and pain points of users and customers.
- 2DefineFrame the right problem to solve.
- 3IdeateExplore several solutions together with the team, before choosing one.
- 4PrototypeMake the ideas tangible as flows and clickable prototypes.
- 5TestTest with users and customers early, and learn before anything is built.
- 6Deliver and improveDevelopment-ready UI, followed up after release.
POS – never slow down the queuefor the cashier taking orders and payments
Cashiers needed to take orders and payments quickly, understand the order at a glance and undo mistakes under pressure. One check was whether a new cashier could take an order and payment unaided.
Design principles
- 1Never slow down the queueEvery tap during the rush has to earn its place.AskCan a new cashier take an order and a payment without help?
- 2Glanceable, not readableStaff should understand the order in a glance, without reading.AskCan staff see what is in the order and what is left to pay in a second?
- 3Forgiving under pressureMistakes happen when it is busy, so they must be easy to fix.AskCan a wrong item or payment be undone without calling a manager?
Table service – eyes on the guestsfor the waiter serving guests at their table
The floor plan and bill needed to help waiters understand table status, hand over to a colleague and handle orders and payments without the screen taking attention away from guests.
Design principles
- 1Eyes on the guestsThe screen supports the waiter, and never takes attention from the guests.AskCan the waiter take an order while still talking to the table?
- 2Every table tells its storyAnyone should be able to pick up a table and know where it stands.AskCan a colleague take over a table without asking?
- 3Follow the guests’ wayThe system adapts to how the guests want to order and pay, not the other way round.AskCan the guests split and pay the way they want, without the waiter working around the system?
Ordering app – help diners get to their foodfor diners ordering and paying from their phone
The white-label ordering app needed to reflect each restaurant’s brand, make ordering quick and show prices and order status clearly. Every step should bring diners closer to their food, without surprises.
Design principles
- 1The brand comes firstThe app is the restaurant’s, not ours.AskWould a diner recognise their favourite restaurant at first sight?
- 2Hungry people have no patienceEvery step should bring the diner closer to the food.AskCan a first-time diner order and pay within a minute?
- 3No surprisesThe diner always knows what they pay, and when the food is ready.AskDoes the diner ever have to ask the staff about the price or the order?
Back office – always show what’s nextfor restaurant owners setting up menus, products and payments
Owners needed to understand what was complete and what remained, and see the result before anything went live. The menu builder used a live preview to show how the ordering app would appear.
Design principles
- 1Self-service firstIf the restaurant has to call support, the design hasn’t done its job.AskCan a new restaurant get through this on its own?
- 2Always show what’s nextThe owner should never wonder what is left to do.AskCan the owner tell what is done and what is left, without help?
- 3Confidence before going liveOwners should see the result as their customers will, before it is published.AskDoes the owner know exactly what customers will see?
Example: how a design principle works
Product design principle
Always show what’s next
- 1User insightRestaurant owners struggle to understand what remains before their restaurant is ready to go live.
- 2Experience principleUsers should always understand their progress, what remains and what action to take next.
- 3Design evaluation questionCan the owner tell what’s done and what’s left, without help?
- 4Design implicationsVisible progress indicators, clear task statuses and contextual next steps.
From principle to decision
Always show what’s next informed guided payment activation that explained KYC and revealed the application status. Confidence before going live shaped the menu builder’s live preview.
The design principles connected what we learned about users to the decisions shaping the products.
- Discovery insightRestaurants couldn’t try the platform, or get started without a sales meeting and help from internal teams.
- Design principleSelf-service first
- Design decisionSelf-service sign-up and a guided onboarding on the dashboard.
- Product direction“We can get started on our own”
- Impact goalA new restaurant gets from sign-up to set-up on its own, without a sales meeting.
- Discovery insightOwners didn’t understand how menus and sales channels connected, and asked support.
- Design principleConfidence before going live
- Design decisionA menu builder with a live preview of the ordering app.
- Product direction“We can build and change our menus ourselves”
- Impact goalRestaurants build and change their menus themselves, without contacting support.
- Discovery insightOwners didn’t understand why KYC was needed, or what was left before they could get paid.
- Design principleAlways show what’s next
- Design decisionThe guide explains KYC, and shows the status of the application.
- Product direction“We get paid from our first sale”
- Impact goalRestaurants activate payouts on their own, so they get paid from their first sale.
Giving four teams ownership of impact, not just delivery
A large part of my work was about how product development operated every day. We had four development teams and two consultant product designers. The teams owned their backlogs together, without separate product owners.
I led roadmap prioritisation, supported sprint goals and helped teams understand problems and own the solutions.
Start with the problem, not the task
A prescribed task might be: Build a form for uploading KYC documents. That defines the deliverable before understanding whether it solves the restaurant’s problem.
I preferred to start with an impact goal: Restaurants should be able to activate payouts themselves so they can get paid from their first sale.
The team could then explore which documents were needed, why the information was required, how the application progressed and what remained. A guiding question was: How might we help restaurants get paid from their first sale without calling support?
That gave the team room to find a better solution than a task list.
A rhythm for learning and delivery
I supported sprint goals, demos, retrospectives and knowledge sharing. Demos offered feedback on both what was built and what teams had learned. I clarified priorities, removed obstacles and stayed close when teams needed support.
- 1RoadmapThemes in order of priority, each with an impact goal.
- 2Sprint planningPlanned the work towards the goal, together with each team.
- 3DemoThe teams got feedback on their work from colleagues.
- 4RetrosLooked back on how we worked, and improved it.
Giving teams ownership through impact goals and design principles
- Add a form with a field for each document
- Add an upload button and a submit button
- Send the files to the payment provider
- Done when the form is live
- “Get paid for what we sell, from the first sale”
- “Understand what is asked of us, and why”
- “Know where our application stands”
- “Do it on our own, without calling support”
Leading without prescribing the solution
I guided two consultant product designers and held one-to-one conversations with them. I wanted to protect room for discovery, exploring alternatives and testing under delivery pressure.
The CTO was line manager for the developers. My responsibility towards the development teams was direction, priorities and the conditions for their work – not deciding every solution.
Connecting dependencies
The menu builder affected the product catalogue, POS, kiosk, app and online ordering. Payment activation depended on an external payment provider and KYC. I coordinated sequencing and made dependencies visible across the platform.
The shift was from teams delivering tasks to understanding what restaurants needed to achieve and owning the way there.
Dependencies across the platform
Most themes touched several products, and some depended on partners outside Baemingo. Owning the roadmap for all products let me sequence the themes across the four teams, so each team knew what it depended on.
- 1“We can get started on our own”Back office: sign-up and the onboarding guide · Account and company data
- 2“We can build and change our menus ourselves”Back office: products and the menu builder · Product catalogue · Menus in the POS, the kiosk, the app and online ordering
- 3“We get paid from our first sale”Back office: payments · The payment provider and its KYC approval
- 4“We can take every kind of payment at the till”The POS at the till · Payments
What we delivered and what we aimed to achieve
What we delivered
- A more connected platform. A new design system and improved interfaces and journeys across products, with technical bugs addressed within roadmap priorities.
- More self-service. Registration and guided onboarding, a menu builder with live preview, and clearer payment and sales-channel activation.
- More payment options. Including cash payments at the till.
- Clearer product direction. A shared roadmap, prioritised impact goals and greater team ownership of solutions.
- A stronger design process. Testable product-specific design principles, discovery and user testing before development.
What we aimed to achieve
- No open critical bugs
- More restaurants getting started independently
- Fewer support contacts
- Shorter time to first sale
- More transactions through Baemingo’s payment services
- Product adoption, retention and business growth
The KPIs in this case are targets, not documented measured outcomes.
Four lessons
Impact goals change the conversation.
A team that understands why a problem matters can explore better solutions than one following a task list.
The design process needs protecting.
Discovery, testing and design systems shouldn’t disappear when delivery pressure increases.
Technical debt and new development must be prioritised together.
They affect the same experience and compete for the same capacity.
Self-service changes more than the interface.
It affects sales, customer success and support, whose knowledge was essential to understanding the problems.
What I took with me
Baemingo taught me to lead product development across multiple products, teams and goals. Above all, I learned the importance of setting direction that’s clear enough for teams to understand what matters most, yet open enough for them to find their own solutions.
As a product and design leader, I want to create a shared understanding of the problem, deliberate priorities and teams with both ownership and room to do good work. That means connecting restaurants’ everyday needs, business growth, technical constraints and user experience quality.
I also want to stay close to design itself. At Baemingo, I did that by leading discovery and design for initiatives including self-service onboarding and the menu builder.
My hands-on product design at Baemingo
I also worked hands-on as product designer on some of the back office improvements. In these cases, I ran the product discovery, designed the user flows and the interface, tested with users and delivered development-ready design.
