Discussions
-
How to Work with AI Agents Without Creating More Noise for Your Team
AI agents are quickly becoming part of daily work. But for most teams, the real question is not whether to use them. It is how to use them in a way that reduces manual coordination instead of adding another layer of noise. If your team already works across Jira, Slack, or Microsoft Teams, AI can be genuinely useful. Not…
-
Improving Time to Value in Jira Starts With Better Workflow Visibility
Atlassian has been clear about where modern teamwork is heading: better alignment, more visibility, and faster progress across teams. In Jira, that usually means making work easier to track, easier to update, and easier to move forward without waiting for someone to manually chase status. And that connects directly to time…
-
Why Teams Confuse Activity With Progress - and What to Measure Instead
One of the most common mistakes in delivery management is assuming that a busy team is a productive team. But activity is not the same as progress. A team can look overloaded every day and still deliver slowly.Why? Because busyness often hides friction inside the workflow: too much work in progress constant context…
-
Using AI to Spot Delivery Risk Inside a Jira Epic
You may see a decent completion percentage, a reasonable number of closed issues, and a sprint that appears to be moving forward. But once you look closer, the picture can change quickly. The remaining work may be concentrated in dependencies, release-readiness tasks, critical bugs, or unowned items that are much more…
-
Activation isn’t onboarding: focus on root-cause value (and your real Aha moment)
I want to share a lesson we learned while building our own product: how to activate users - one of the most fundamental problems for any SaaS. Because without activation, there’s no sustainable growth. Activation usually comes down to two things Defining the Aha moment Reducing Time to Value (TTV) In theory it sounds…
-
Jira Sprint Velocity: Why the Number Alone Isn’t Enough (and How AI Helps)
Sprint velocity is one of the most common Scrum metrics in Jira. But the problem is: most teams stop at the number. You finish a sprint, see velocity dropped, and the discussion starts: * did the team slow down? * was planning off? * did we have blockers? * was scope different? That’s the real issue with velocity in Jira.…
-
Is Evolution Just a Slow Revolution?
In managing a product, a team, a company - or even yourself - I almost always see two camps. The evolutionists. They believe change should be careful. Gradual. Step-by-step. “Don’t break it - improve it.” “Let’s avoid sharp moves.” “The system needs time to adapt.” And then there are the revolutionists. “Cut it now.”…
-
Using AI to Diagnose Workflow Bottlenecks in Jira (Beyond Sprint Reports)
When it comes to analytics, many teams rely on sprint metrics - velocity, planned vs completed, commitment reliability. But sprint reports don’t always explain what’s actually happening inside the workflow. We approached it a bit differently. Instead of analyzing a sprint, we asked AI to analyze flow behavior over time in…
-
The Consistency Principle and the “Low-Ball” Effect in Agile Teams
Agile teams value transparency, adaptability, and learning from reality.But in day-to-day work, teams often fall into a subtle psychological trap that works against these principles. It’s known as the low-ball effect, and it is driven by a deeper mechanism - the principle of consistency. What is the low-ball effect? It…
-
Metrics as a Verdict: Why Startups Avoid Reality
In my consulting work with startups, the first and hardest barrier is almost always the same: the shift from unconditional belief in the idea to reliance on measurable feedback. Teams often genuinely love their product.They invest energy, identity, and meaning into it. But belief alone doesn’t move a product forward.At…
-
Agile’s Intersubjective Reality in 2026
The beginning of a new year is a good moment to step back and look at how we actually make decisions in Agile teams. We often talk about two realities: Objective - metrics, delivery speed, cycle time, incidents, facts. Subjective - opinions, team feelings, personal experience, intuition. But in practice, Agile teams…
-
The Student Syndrome: Why Agile Teams Delay Work Despite Better Tools - and How AI Makes It Worse
In Agile teams we constantly talk about velocity, sprint planning, estimates, and delivery flow. Yet even with mature processes and excellent tooling, teams keep missing deadlines and burning buffers for the same simple reason: work starts too late. Project management literature has long described multiple syndromes that…
-
AI Is Rewriting How Teams Use Jira. The PLG Era Is Over.
Why This Matters for Teams Working in Jira For the past decade, much of the Atlassian ecosystem followed a familiar motion:install an app → enable features → boost productivity. But many teams now face: cross-functional workflows that outgrow the original Jira setup rising volumes of service and operational work manual…
-
The Identity Trap: Why Fixed Identity Breaks Agile Teams
I love psychology for its paradoxes - especially the ones that show up not in therapy rooms, but inside teams and leadership discussions. One of the most common scenarios I see looks like this: A person or a team comes with a complaint: “We’re stuck. There’s no real progress.” The response is almost always the same: Let’s…
-
How to Reach the Top 25% — and Why It’s Enough
There’s an old idea, repeated in different forms by Charles Duhigg, Naval Ravikant, Scott Adams, and James Clear:Almost anyone can become part of the top 25% in a given field — if they find the right intersection of their strengths. Why the Top 25% Matters We often think success means being the best — the top 1%.But in…
-
The Focus Dilemma: Why “Double Strategy” Fails in Agile and Business
In Agile teams, we often face a familiar trap: trying to be everything at once.Leaders want startup speed with enterprise reliability, premium quality with low cost, or broad market reach with niche specialization — all at the same time. This is the same trap that Michael Porter, one of the most influential strategists in…
-
How to Replace Daily Standups in JIRA — the Async Way
The Hidden Cost of Daily Standups TimeframeStandup DurationTeam SizeTotal Time per PersonTotal Team TimeEquivalent in Workdays (8h/day)Daily15 minutes1015 min2.5 hours/day0.3 days/dayWeekly15 min × 5 days1075 min (1.25 h)12.5 hours/week1.6 days/weekMonthly (≈4 weeks)15 min × 20 days105 hours50 hours/month6.25…
-
Agile as Will and Representation
I’ve always loved Schopenhauer’s The World as Will and Representation.It’s pure philosophy — but also, surprisingly, one of the best metaphors for modern management and Agile practice. He believed that everything in the world exists in two dimensions: will (the drive behind action) and representation (how we perceive and…
-
Kanban Is Not a Board — It’s a Sense of Purpose That Moves the Team
Let’s talk about crisis moments.Because the way teams act under pressure often reveals what Agile truly means — not just as a framework, but as a mindset. There’s one story I always come back to.It’s from 1972, when Southwest Airlines had… $143 left in their bank account.That’s not a typo. $143 — and a fleet of four…
-
Good Strategy vs. Bad Strategy
(based on Richard Rumelt’s framework) Good strategy always has 3 elements: * Diagnosis — clear definition of the problem or challenge. * Guiding policy — an approach that sets direction and limits options. * Coherent actions — concrete steps aligned with the policy. Bad strategy looks different: * A list of abstract goals…
-
Good Strategy, Bad Strategy — and Why Real Strategy Emerges from the Ground Up
In strategic management, the biggest myths are not about what to write in a strategy document, but how strategy is actually born. Many founders and managers believe strategy should come from the top. In practice, that belief often leads to stagnation and a vacuum — where people wait for direction while reality changes…
-
Why OKRs Often Fail: Three Lessons from Practice
When helping companies adopt OKRs (Objectives and Key Results), I’ve seen the same challenges repeat again and again. Here are three observations that might sound familiar if you’ve worked with OKRs yourself: 1. Underestimating the need for system OKRs are not just a tool for setting goals. They’re a framework that…
-
Faster focus, less overhead: NCT for Agile Startups
When your team is small and priorities change every week, OKRs often feel too heavy. You want focus and alignment, but not the overhead of a rigid framework. That’s where NCT comes in: Narrative – Commitments – Tasks. It’s a lightweight structure that helps early-stage teams stay aligned while moving fast. How it works…
-
Loom app for Mac – interface not showing up
Hey everyone~ Quick question about the Loom app for Mac (desktop version). Every time I start recording, the Loom interface disappears – which is normal. But before, I could just click on the Loom app again and it would stop the recording and bring the interface back. Now, that doesn’t work anymore. If I click the app,…