Product Management

Like a snowball rolling downhill, technology debt simply gets bigger.

Cutting corners and patching things up work for a while. But eventually the codebase becomes a mess. Features take longer to build, and bugs pile up. The team becomes nervous about making changes. This triggers leadership demands speed, trapping everyone in a difficult cycle to break.

There are two types of product teams - the slow-learning and the fast-learning.

The slow-learning team wants to deliver. They manage projects, write tickets, attend internal meetings and ask colleagues for design feedback. They mostly care about delivery and managing expectations.

The fast-learning team wants to learn. They talk to customers, read market news, push hacky code to production, and sometimes break things. They embrace ambiguity, but they learn fast.

The difference? The slow-learning team builds products for their bosses, and the fast-learning team builds products customers actually need.

Shift your focus. The best products come from deep insight, not just efficient delivery.

When your team isn't experimenting enough, it's most likely due to experiments taking too long to build, track and measure.

But every missed experiment is a missed opportunity. Insights go untapped. Ideas remain untested. Innovation stalls.

If the bottleneck is tech, hack it. Find workarounds even at the cost of degrading user experience but push forward.

Constraints spark the best solutions.

Product Managers own the full lifecycle - strategy, discovery and delivery. Product Owners focus narrowly on Agile delivery. Splitting these roles fragments accountability and muddies product development.

True impact comes from roles with full ownership.

Engineers love clarity. The most important problem defines the mission.

A disjointed list of tickets signals confusion, while a vague objective offers no direction. Great work emerges when the goal is clear, focused and free of jargon.

When the problem is precise, teams know exactly where to aim.

Not every team needs a dedicated PM. Someone is already handling the PM work informally. It's not complex.

Eventually, though, clear ownership becomes unavoidable. Is an individual contributor juggling alignment, communication and strategy alongside their core work? Or is it time to delegate those responsibilities to someone focused entirely on them?

The decision shapes how the team prioritises and executes.

A great product isn't just a checklist of requirements. It's built by understanding the customer's problem and why it actually matters.

Don't just follow instructions. Look deeper. Ask why. Question the logic.

The best solutions come from people who do a bit of detective work, not just execute.

Side projects teach product management faster than any course.

Finding a problem, crafting a solution and marketing it sharpen critical skills. You learn to balance creativity with practicality and adapt to real-world feedback.

Hands-on experience builds stronger product managers.

Great ideas are crafted, not found.

They come from clear problems, real insights, diverse perspectives and bold inspiration. Ideation sessions - prep, sketch and develop. Turn this mix into better solutions and stronger buy-in.

Prep sets the stage. Sketching sparks creativity. Development refines ideas into actionable next steps. Keep it sharp and ideas will shine.

Removing a feature signals a mistake. Few people feel comfortable admitting that.

This hesitation keeps bad features alive. Teams cling to them, fearing the optics of walking back a decision. But doubling down on something that doesn't work costs more in the long run - time, energy and user trust. Recognising when something doesn't fit and cutting it isn't failure. It's progress.

Users notice when products improve. Removing what's broken clears space for what works.

The exec team was drifting, priorities misaligned, goals scattered. With OKRs, we trimmed 50 key results to 15, forcing clarity on what mattered most. The tough trade-off conversations exposed clashing perspectives but created alignment. Had to be done.

In product management, it's tempting to move fast and break things. Sometimes, that works.

But moving with purpose works better. It means focusing on what matters, making smart choices, and building something valuable. Speed without direction leads to wasted effort. Purposeful action builds progress that lasts.

Fast fades. Purpose wins.

Saying no is a leadership skill.

It's not about rejecting ideas, it's about protecting focus. When everything feels important, nothing is. Saying no clears space for what truly matters - what drives impact, not just activity.

Yes, it will sting. People will take it personally. But prioritisation isn't about popularity; it's about progress.

Every “no” to distractions is a “yes” to momentum.

Bold ideas unlock progress.

When crafting new products or features, it's easy to focus on safe, incremental improvements. These solutions feel achievable and practical but they rarely break new ground.

Adding a bold concept into the mix forces the team to think beyond limitations. Even if the daring idea doesn't make it to launch, it creates a spark. It pushes boundaries, reshapes how problems are viewed and reveals opportunities overlooked in safer designs.

A bold solution isn't just a backup plan. It's a catalyst for better work.

Quite often you see founders say they want the product off their plate. Sure. But nothing tests it better than the first Head of Product hire, essentially creating a two-headed product leadership for a time. And this can backfire.

The challenge comes from the founders' deep knowledge of the space. They know their customers; they meet them often. They know the weird edge cases and how to get around them. They know why and how certain things were built and why other things never got done.

But as the company grows, the founder gets pulled everywhere, every day. Founders typically deal with a few different things: fundraising, hiring, culture, operations, strategy, customers and board updates. That's enough to give anyone anxiety.

The cracks show up in the work first. That's when the company starts needing product leadership outside the founder's head.

Not to grab the wheel.

The goal is not to turn the company into a corporate machine (even though it might be needed down the road), but the goal is to replicate, per se, the founder's product instincts while making them available to the rest of the company.

When it works, both help the company scale without losing what made it special in the first place.

A team doesn't always need a dedicated product manager.

In startups, founders often take on this role naturally, using their deep understanding of the market and their vision for the product.

In larger companies, if the team already has a strong handle on strategy, data and market needs, they can absolutely operate without a formal PM. However, someone still needs to take charge of the product function - making prioritisation decisions clear and aligning the team around common goals.

Feature prioritisation isn't always about frameworks like ICE (Impact, Confidence, Effort), Kano or MoSCoW.

Sometimes, it's about creating buzz, lifting your team's morale, staying ahead of competitors or even strengthening internal relationships.

The challenge is finding the balance between chasing these quick wins and staying true to your long-term vision.

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.