TL;DR

Role clarity is oxygen. Let PMs own direction and PDs own experience. Protect calendars, write before debating, adjust volume by phase and track one metric that matters. Ship faster, sleep better.

1. Draw the Line Early

Product Manager (PM)

• Core focus: market and viability risk
• Typical questions: “Will people pay for this?” “Does it move the North-Star metric?”
• Key output: one-pager covering purpose, success metrics and trade-offs

Product Designer (PD)

• Core focus: usability and desirability risk
• Typical questions: “Can customers complete the task?” “Where do they stumble?”
• Key output: clickable prototype showing flow, copy and edge states

2. Guard the Calendars

Red flag: PM trapped in Figma tweaking icons. Red flag: PD buried in cost–benefit spreadsheets. Fast filter:

• If the task changes product vision, it belongs to the PM.
• If the task changes product surface, it belongs to the PD.

This discipline frees the roadmap and keeps creative energy high.

3. Write First, Talk Second

• PM posts a succinct one-pager to Slack outlining problem statement, success measures and known constraints.
• PD replies with a Figma link showing interactive flow, micro-copy and empty-state behaviour.
• Only then schedule a 30-minute debate. Decisions lock in, iteration time halves.

4. Phase-Based Volume Control

• Framing / Discovery – PM's voice dominates; market-sizing memo appears.
• Ideation & Prototyping – PD leads; high-fidelity Figma frames drop.
• Build & Polish – PD still loudest; design-system tokens freeze.
• Launch & Iterate – PM turns the volume back up; KPI dashboard lights up.

5. Share One Scorecard

Choose a single, public metric - activation lift, task-success rate or first-week retention. Both crafts pull the same lever, killing silos and politics.

6. Outcomes You Can Expect

• 25–40 % faster time-to-decision (anecdotal data from five Aussie SaaS teams).
• Higher designer morale: fewer context switches, deeper craft.
• Sharper product bets: PMs stay market-obsessed, avoiding “feature museum” creep.

Recommended Tools & Rituals

• Figma for rapid prototypes (PD).
• Miro/FigJam for story mapping (shared).
• Amplitude or Mixpanel for the single metric (PM).
• Weekly 15-minute “Line-Check” stand-up: confirm who owns which decisions this sprint.

Working at a small tech business shapes your career differently.

You'll juggle strategy, customer service, product development and beyond. The small team demands versatility, immersing you in every aspect of the business. This hands-on experience accelerates learning and builds skills quicker than larger organisations ever could.

For ambitious minds craving growth and variety, nothing compares.

If the user experience needs explaining, it's not a good one.

Clarity should be baked into design. The best experiences guide users seamlessly, answering questions before they arise and making every interaction intuitive.

Explanations only highlight what's broken. A great user experience speaks for itself.

Pedestrian crossing or not?

Tactical decisions for short-term revenue often clash with long-term strategy. They're unavoidable in business. Balancing these moments without losing sight of the bigger picture defines strong leadership.

Love this quote from "Ego is the Enemy" by Ryan Holiday as it helps stay humble and open to feedback from others.

The first principle is that you must not fool yourself - and you are the easiest person to fool.

Dedicated QA creates more problems than it solves.

When a dev team owns quality, accountability stays in the right hands. Bugs are fewer, fixes are faster and processes tighten.

Introducing dedicated QA shifts that balance.

Developers grow complacent, relying on testers to catch mistakes. Tools diverge, creating inefficiencies. QA often duplicates what devs should already handle.

Quality isn't a separate role. It's a shared responsibility embedded in every line of code.

TIL: "Lighthouse Customers" - customers who get a better or discounted rate on your product in exchange for regular, meaningful feedback.

Lighthouse customers give you a strategic edge. These early adopters don't just use your product - they help shape it. Their feedback highlights gaps, confirms your direction, and sharpens your focus. In return, they get early access to a solution that feels designed just for them, often at a special rate.

Ambiguity makes people freeze. But it doesn't have to.

Not knowing what's right or what's next stalls. That hesitation drags. Pair reflection with motion - thinking and doing - and clarity shows up faster than you expect.

Track your bets. Review what worked and what flopped. But keep moving. You don't need perfect answers. Just honest ones. Then act.