Mohammed Hussain · Senior Product Designer
Fintech, SaaS, and AI. Four companies. One pattern — I tend to be the person who goes from zero: zero design team, zero framework, zero system. And stays until it ships.
One person running marketing across 5–50 locations. Non-technical. Time-poor. Lives in spreadsheets and group chats.
One person running reservations, covers, guest data, ops — often across multiple concepts. Non-technical. Time-poor. Same human.
Each case study includes a live Figma prototype walkthrough — I'll share the link when we get there.
How do you compress a week of multi-location content work into under two minutes — without losing brand voice, approvals, or audit trail?
Form fields asking "what do you want to post?" didn't help. They needed a thinking partner, not a template.
Ten locations, ten slightly different voices. Corporate chasing compliance, franchisees improvising.
Screenshots forwarded over messages, no audit trail. Nobody knew who approved what.
Solo designer · PM & I ran 8 customer calls · 2 shadowing sessions · competitive review
Every competitor used form-based briefs. Jasper, Hootsuite, Buffer — all the same. We'd just moved the problem one step earlier.
The fix wasn't a better form. It was not a form.
Covers the full flow: brief → multi-format generation → review & edit → approval → publish & audit.
Let users self-select. 65% chat, 35% form, similar completion rates. Both needed.
A 10-person team and a 500-location franchise need different routing. One checkbox serves neither.
Enterprise customers asked week one. Shipped within the first month after launch. For a multi-location team product, audit trail is table stakes.
We designed for team workflows. People needed their own view first. Teams are made of individuals.
Birdeye had no design language for AI agents. Lead Gen was the first — but I designed the framework first. Multiple agents now use it across the org.
Every competitor gave operators a prompt box. Wrong mental model for a non-technical operator running ten locations. They don't write prompts — they hire people.
Solo designer · PM · ML Engineer · CS team · customer testing
The mental model shift: configuring an AI agent should feel like briefing a new hire — not programming a bot.
That's where Goals → Triggers → Tasks came from.
Covers: Goals → Triggers → Tasks configuration, reusable tool primitives, Lead Gen agent in action, outcomes dashboard.
Non-technical operators don't write prompts. They configure outcomes. Same model now runs every agent across the org.
Operators need to understand what the agent is doing before they'll deploy it. Transparency = trust.
I treated ML as a cost constraint early. They see model failure modes I'd never catch in usability testing. Start there next time.
"Goal" beat "objective." "Task" beat "action." I spent as much time on language as on screens.
Reservation demand is still demand generation. Events, seasonal menus, promos, and local discoverability all need tools that help operators move fast without losing control.
The same systems thinking applies to structured workflows like waitlist management, service recovery, table turns, or handoffs between automation and staff.
What makes restaurants special is that the system still has to support warmth: remembering preferences, preserving context, and helping staff feel more personal, not more robotic.
The reason this role makes sense to me is that it sits at the intersection of operations, growth, and guest experience. That is exactly where I like to design.
Happy to go deeper on anything — research method, specific design decisions, trade-offs with ML, post-launch learnings, or how I'd approach OpenTable problems.
hussain.design · hussain.ux@outlook.com · linkedin/hussainhida