Delivery risk
Velocity is up. Trust is down. Teams comply in meetings and reject the system in practice.
- Green dashboards, fragile delivery
- Ceremony load crushing the day job
- Best people quietly leaving
For CEOs, COOs, CHROs, and transformation sponsors
Your rollout can look green while your people are breaking.
If your rollout looks green and your people do not, you are in the right place. I built the Human Agile model and Index after years inside enterprise agile work. Below you will find the budget gap, what Jira-style transparency does to team freedom, and what our survey keeps revealing. No firm behind this yet. Just me. Background on anjishbhondwe.com.
What keeps leaders awake
These are not maturity scores. These are the things that keep showing up when the programme office thinks it is winning.
People risk
HR sees stress the programme office does not measure. Retros become tracking, not learning.
- Burnout treated as individual failure
- Honest feedback punished
- Training that never sticks
Scale risk
The next rollout copies what looked successful on slides, not what actually worked with people in the room.
- Framework bought before humans consulted
- CoEs optimizing reporting, not enablement
- Dark Agile spreading across business units
The socio-technical tension
Every transformation runs two systems at once. Most enterprises only fund one.
Every transformation runs two systems. The technical one is loud: tools, velocity, dashboards, milestones. The social one is human: trust, safety, belonging, honest feedback. Fund one without the other and people pay. That is not a culture side issue. That is the design failure.
When budget and timeline own the rollout, interviews name the same harm differently: Dark Agile, forced agile, fake agile. Same wound. Different programme language. Tool governance is where I see sponsors lose the plot most often.
When transparency becomes control
Jira, portfolio views, and funding dashboards gave sponsors a live read on every sprint and spend line. That can be fair. It turns forced agile when paying for the programme is treated like owning the team.
Funding a rollout is not the same as owning the humans inside it.
Legitimate sponsor role
- Fund outcomes and guardrails
- Review risk at human gate checkpoints
- Ask whether value and safety are both emerging
- Hold leaders accountable for system design
Overreach (Dark Agile pattern)
- Monitor micro-spend and velocity continuously
- Use dashboards to override team judgment
- Treat retros as tracking, not learning
- Punish honest signal as programme disloyalty
Before these tools, sponsors saw milestones and spend at programme level. Now leadership often sees every epic and burndown in real time, while teams get no equal say on whether the programme is safe to speak in or sane to carry. Visibility went up for sponsors. It did not go up for trust.
I am not against accountability. I am against execution funding becoming control over daily team life. The human gate exists because programmes skip that conversation once the board goes green.
Are your dashboards for learning, or for judgment? The Human Agile Index™ asks that before the next scaling wave.
Human impact under forced transformation
From our anonymous field survey across telecom, financial services, retail, and tech. These are not industry benchmarks. They are what respondents said when we asked what the rollout did to them.
I have sat with strong delivery teams that were shutting down mid-transformation: green velocity, solid record, humans breaking. These charts pair where attention goes with what that costs people.
- Dark Agile dashboard theater
- Forced agile budget-dictated rollout
- Fake agile ceremony without belief
From programme reviews I sat in. Mirrors the 37-point people gap on the home page.
Share of interviewees who named each impact. Not a census of all IT workers.
Burnout or sustained overload
Chronic exhaustion, sprints stacked on unfinished work, crying in bathrooms while dashboards stay green.
Motivation loss
Comply in meetings, reject the system in practice. Ceremony without belief.
Continuity risk
Attrition intent, knowledge walking out, best people managed out after honest retros.
Top performers, parallel strain
Teams leadership flagged as high velocity who reported shutdown under forced rollout waves.
How we ran the survey. Anonymous interviews across telecom, financial services, retail, and technology. Percentages are share of respondents who named each impact, not a census of all IT workers. Budget figures come from programme reviews I attended. This is our field read, not peer-reviewed industry data. Cite: agilefragile.com/leaders.html#human-impact.
What our survey reveals
Anonymous voices from our field survey. Different sectors. Same wound. Not people complaining about agile. People describing what happened when the social system broke and the dashboard stayed green.
"I was burnt out before the transformation. After it, I had sprints on top of the work I already could not finish."Engineer, financial services
"We had a two-hour agile training. Then we were measured on velocity every week. Nobody asked if we understood why."Product team member, retail
"I raised concerns in the retro. Two months later I was managed out. The retro is not for learning here. It is for tracking."Developer, telecom
"Leadership sees green dashboards. We see people crying in the bathroom. Both are true in the same building."People lead, technology
Leaders and scholars who put humans first
Human-centric agile is not a brand position. It is what the founders, practitioners, and researchers said when they still had the room's attention.
Individuals and interactions over processes and tools.Beck, Cockburn, Fowler, Jeffries, Sutherland, and twelve others
Psychological safety is a belief that one will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes.The Fearless Organization, 2018
People's characteristics are a first-order success driver, not a second-order one. In fact, I have reversed the order, and now consider process factors to be second-order issues.Characterizing People as Non-Linear Components, 1999
If you want to succeed in doing software development, you need to find good people that work together at a human level, so they can collaborate effectively. The choice of what tools they use or what process they should follow is second order.The State of Agile Software, 2018
The hard part of software design is navigating the human relationships, full of conflict and conflicting incentives.Software Design is Human Relationships, 2023
The only thing of real importance that leaders do is to create and manage culture.Organizational Culture and Leadership, 2010
What the model offers leaders
A human-first operating lens for enterprise transformation, not another framework rollout. The model helps name what is breaking people, strip what harms, and scale what works with employees in the design, not on the receiving end of a programme timeline.
Who is behind this
Anjish Bhondwe
Agile Fragile is the public home of the Human Agile model. I am proposing it based on years of enterprise agile scaling work across federated organisations, CoEs, and multi-country programmes.
For full background, credentials, and client work, visit the personal site. There is no team page here because there is no team yet.
A straight conversation
No pitch deck on the first call. I listen to what is happening to your people. Share your Human Agile Index score if you have one. I will tell you honestly if a conversation makes sense.
Start a conversation