Product leaders spend a lot of time translating complexity: competing stakeholder visions, messy workflows, architectural constraints, customer needs, commercial realities, and assumptions that have never been made explicit.

Talking about those things is useful. But sometimes conversation alone allows ambiguity to survive.

Give people something concrete to react to

Earlier in my career, I was working on a new patient scheduling product with a CEO, CTO, and Product Director who each had a different idea of how the experience should work.

I could have continued facilitating the debate. Instead, I mapped each proposed experience end to end, printed the flows, and put them side by side on the table.

Suddenly the conversation was different. The complexity was no longer theoretical. Everyone could see how many steps, branches, dependencies, and exceptions each idea created. The simpler path became much easier to agree on because the tradeoffs were visible.

Tangled flow versus clean flowTwo scheduling workflows drawn as flowcharts. The first, the flow the executives described, has many steps and decision points, with paths that loop back and cross. The second, the proposal, is a short path with a single decision whose two branches rejoin before the end.The flow they describedEvery branch, dependency, and exceptionThe proposalA short, clean path to bookTangled flow versus clean flowTwo scheduling workflows drawn as flowcharts. The first, the flow the executives described, has many steps and decision points, with paths that loop back and cross. The second, the proposal, is a short path with a single decision whose two branches rejoin before the end.The flow they describedEvery branch, dependency, and exceptionThe proposalA short, clean path to book

Artifacts can act like a mirror

A useful artifact does more than communicate your recommendation. It reflects the system back to the people inside it.

A workflow map can expose how much friction we are asking users to tolerate. A portfolio map can reveal overlapping products or unclear positioning. An architecture diagram can show where a supposedly small request creates dependencies across half the system.

That matters because people often defend an idea differently once they can see its consequences.

The artifact should clarify, not decorate

I am not talking about making prettier slides.

The value comes from choosing a representation that makes the real decision easier to understand. Sometimes that is a flowchart. Sometimes it is a prototype, a matrix, a journey, an architecture map, a pricing model, or a side-by-side comparison.

  • Flowchart
  • Prototype
  • Matrix
  • Architecture map
  • Pricing model

The format matters less than the question it helps answer.

A strong artifact reduces the amount of interpretation required before people can discuss the actual tradeoff.

Show the consequence, not just the recommendation

I have found this especially useful when I am asking an organization to change direction.

Telling someone an approach is too complicated invites debate. Showing the complete workflow lets them inspect the complexity for themselves. Saying a portfolio is fragmented is subjective. Mapping the buyer, use case, overlap, and dependencies makes the fragmentation harder to dismiss.

That distinction matters. People are generally more willing to act on a conclusion they helped reach than one they feel was handed to them.

Creative communication is part of product leadership

Product work is full of situations where the evidence exists but the organization has not yet internalized what it means.

Part of the job is finding the form that makes the insight land: the picture, prototype, model, narrative, or demonstration that turns an abstract concern into something people can understand and act on together.

The goal is to make the problem so clear that the right conversation becomes hard to avoid.