Agile Journeys is an ongoing series of candid conversations with Agile practitioners, product leaders, and transformation thinkers across the Atlassian ecosystem. Each conversation explores the realities behind Agile delivery — the decisions, trade-offs, patterns, and human dynamics that shape how modern teams actually work.
Our goal is simple: surface practical, experience-driven insights from people living Agile every day.
In this edition, we sat down with Marc Brickley, Product Manager at Moser IT, and creator of ClearPath for Jira, whose career spans defense software, Silicon Valley collaboration technology, enterprise Agile delivery, and — perhaps most unexpectedly — youth sports coaching.
What quickly became clear in our conversation: Marc’s thinking about Agile, product development, and visualization is deeply rooted in one central idea:
Agile is ultimately a human system.
Marc’s early career began far from the startup world many associate with Agile.
“I started in the defense industry,” Marc explains. “Very traditional waterfall. Very long timelines.”
The problem wasn’t technical feasibility.
It was delivery latency.
“A pilot could request something that might genuinely improve safety — something we could build in weeks — but they wouldn’t see it for years.”
That experience exposed a fundamental tension:
When feedback cycles stretch too long, value becomes theoretical.
Agile, for Marc, initially represented not speed — but relevance.
Delivering something while it still matters.
Later, working in Silicon Valley at Prism Software, Marc encountered the opposite challenge.
Here, priorities could change instantly.
Ideas could ship rapidly.
But with that freedom came friction.
“Just because you can pivot constantly doesn’t mean you should.”
Too much fluidity created noise.
Too many shifts created cognitive overhead.
Teams weren’t blocked by process — they were blocked by strategic volatility.
This dual exposure — rigid waterfall vs unmanaged Agile — shaped Marc’s balanced view:
Agility requires adaptability and clarity.
Marc originally trained as a developer, but quickly discovered his natural strength.
“I wasn’t the best coder,” he says candidly. “But I was very good at breaking down complex problems.”
That capability — decomposing complexity — would later define both his product thinking and his approach to Agile systems.
Because at scale, Agile challenges are rarely about tools.
They’re about understanding complexity clearly enough to act.
The origin of ClearPath reflects this mindset.
During COVID, Marc faced a high-stakes delivery scenario with a client where teams believed timelines were impossible.
Rather than escalating or negotiating, Marc visualized the dependencies.
“I mapped everything out,” he recalls. “What depends on what. What blocks what.”
That single visualization reframed the conversation.
From abstract debate → concrete reasoning.
ClearPath emerged not as a reporting layer, but as a cognitive amplifier.
A way to help teams reason about complexity visually.
Marc emphasizes that dependencies are not merely structural artifacts.
They are communication mechanisms.
When dependencies stay implicit:
• Teams argue conceptually
• Risks surface late
• Planning becomes reactive
When dependencies become visible:
• Conversations shift from opinion → reasoning
• Bottlenecks emerge early
• Alignment accelerates
Visualization, in this sense, becomes a leadership tool.
Not for control — but for shared understanding.
One of the most compelling aspects of Marc’s perspective is how strongly he distinguishes product thinking from project thinking.
Project management optimizes execution.
Product management optimizes decisions.
“In product management, you’re constantly asking: did we achieve the outcome?”
Velocity, throughput, burn-down charts — useful signals.
But insufficient proxies for value.
For leadership, Marc argues, outcomes matter more than output metrics.
Perhaps the most fascinating dimension of Marc’s journey lies outside software entirely.
Marc spent years coaching youth sports — an experience that profoundly shaped his leadership philosophy.
“When you coach kids,” Marc explains, “you can’t rely on authority. You have to rely on trust.”
Motivation cannot be mandated.
Engagement cannot be enforced.
Learning cannot be imposed.
The parallels to Agile leadership are striking.
Coaching, mentoring, product leadership — all require influencing without command-and-control structures.
“It’s always about people,” Marc notes. “Always.”
Marc also channels his thinking through writing.
His blog, The Product Ref, explores product ownership, estimation, Agile thinking, and delivery dynamics through a practical, reflective lens.
Rather than prescribing frameworks, Marc focuses on decision quality and clarity of thought.
In The Beauty of Story Points, he reframes estimation debates away from precision toward shared understanding:
Story points are not forecasting tools.
They are conversation tools.
Similarly, in Don’t Forget It’s a Story, he highlights how easily teams reduce work items into tasks while losing narrative context.
Across his writing, one pattern is consistent:
Agile effectiveness is driven by how humans interpret and coordinate work — not by the mechanics of the framework itself.
Visualization plays a particularly powerful role in backlog refinement.
Refinement sessions often struggle under invisible complexity:
Hidden dependencies
Unclear sequencing
Ambiguous effort assumptions
Visual mapping reduces cognitive load.
It transforms refinement from estimation rituals → system design conversations.
And increasingly, this raises a larger enterprise question:
Where should Agile thinking live?
Modern Agile teams frequently distribute ceremonies across external tools:
Whiteboards
Spreadsheets
Chat platforms
While flexible, this fragmentation introduces systemic risks:
• Context loss
• Traceability gaps
• Governance friction
• Data invisibility for AI systems
When ceremonies move inside Jira:
• Insights attach directly to execution
• Permissions inherit security posture
• Context remains durable
• Continuous improvement becomes frictionless
This is where ClearPath and Agile Retrospectives naturally converge:
Visualization + Reflection
Dependencies + Learning
Planning + Adaptation
All within the system of record.
Marc highlights an unexpected benefit of dependency visualization tools.
They upskill product owners.
They encourage thinking not just about:
Why we build something…
…but how reality constrains delivery.
A subtle but critical shift toward systems thinking.
Marc’s career arc offers a refreshingly grounded Agile narrative.
Defense waterfall → Silicon Valley flexibility → enterprise Agile → product creation → youth coaching → writing
Agility is not rigidity.
Agility is not chaos.
Agility is managed adaptability anchored in human understanding.
Tools clarify.
Visuals align.
Metrics inform.
But people decide.
Always.
✨ Key Takeaways
Visualization transforms complexity into shared understanding
Agile failures often stem from invisible dependencies
Product thinking prioritizes outcomes over activity metrics
Coaching and Agile leadership share the same human foundations
Story points and metrics are conversation tools, not control tools
Governance improves when thinking stays inside the system of record
Follow Marc Brickley on LinkedIn and explore The Product Ref for deeper reflections on product ownership, estimation, and Agile decision-making.
And as always, discover more perspectives in the Agile Journeys series on the Catapult Labs blog.
Marc Brickley is a Product Manager, Agile practitioner, and creator of ClearPath for Jira. He has worked across defense software, Silicon Valley product teams, and enterprise Agile environments, and shares his thinking on product leadership through his blog, The Product Ref.
ClearPath for Jira is a Jira app that helps teams visualize dependencies across their backlog. By making relationships between work items visible, it enables better planning, clearer conversations, and more effective backlog refinement sessions.
Dependencies are often the hidden source of delays in Agile delivery. When they are not visible, teams make decisions based on incomplete information. Visualization helps teams identify bottlenecks early, understand sequencing, and align more effectively during planning and refinement.
According to Marc, project management focuses on executing a predefined plan, while product management focuses on deciding what should be built to achieve meaningful outcomes. Product thinking is outcome-driven, whereas project thinking is typically task and delivery-focused.
Many Agile teams rely on multiple external tools for retrospectives, planning, and collaboration, which leads to fragmentation and context loss. Bringing ceremonies back into Jira helps centralize work, improve traceability, strengthen governance, and reduce friction between discussion and execution.