Editorial
Research Report
The State of the Digital Workplace
"I write only when inspiration strikes. Fortunately it strikes every morning at nine o'clock sharp."
Who doesn't love this quote? Whether William Faulkner or W. Somerset Maugham said it, the quote captures what most people get wrong about inspiration. We think it's mystical. But really, it's methodical.
I don't write novels. My craft is organizational success. And in my realm, the most misunderstood thing is accountability. Typically, we treat it like blame. When in reality, it’s about preparation. In its truest form, it's fortification against failure, not a consequence for it.
We invoke accountability after things fall apart. But the real work happens well before.
Something goes wrong. A product launch misses. A deadline slips. A client escalation lands on the wrong desk. And a senior leader, frustrated and under pressure, asks: "Who is accountable for this?"
Asked in this way, it's the wrong question. The moment for real accountability has passed.
The Problem With Always Being Green
I was working with a tech company gearing up to launch a compelling new product in the global marketplace. The product team built a roadmap with a clear launch date across 12 markets. Sales and marketing scheduled their supporting activities accordingly. Marketing started building collateral and putting it into the marketplace. Sales started talking to global customers, teasing the product and building enthusiasm.
At every status meeting, the product team insisted all was trending well. Everything was green in their status reports.
The launch date came and went. Suddenly all that green was now red.
Turns out the complexity of launching in so many markets at once, all the legal and compliance work, was never going to be doable on the committed timeline. But sales and marketing knew something product didn't. Of those 12 markets, two accounted for most of the demand. Had the product team been open about what they were struggling with, the three teams could have collectively agreed to focus on the two key markets and actually hit those deadlines.
Instead, they disappointed customers in 12.
Product believed that "showing their yellow" equaled owning failure. They lacked the skills required, and senior leadership would be angry. But that belief cost them the chance to actually succeed.
Another client said it perfectly: "Everything is green until it's red." We never hit yellow. We skip right past the early warning signs, the concerns that are still manageable, the problems you can see coming if you're paying attention. We pretend things are fine until it's too late to pretend at all.
Why Yellow Is Where the Magic Happens
Organizations or teams that are always green likely aren't setting sufficiently aggressive goals. The yellow zone is hugely undervalued. It tells us we're stretching and challenging ourselves. It's the space where shared brainstorming and problem-solving should come to life.
But instead, we fear it. We see yellow as an indicator we're heading toward failure, so we try to hide it.
This is backwards. Good yellow behavior isn't saying "I'm a failure." It's saying "I'm being vigilant, watching closely and committed to success. I see complexity showing up. I've failed at nothing, but I'm observing some concerns. Let's share what we know and figure this out together."
Yellow is the most valuable signal a team can produce. But you only get it if people believe that surfacing a problem is an act of ownership, not an admission of fault.
When accountability only shows up as punishment, people learn fast. Raising a concern feels like volunteering for blame. Flagging a risk feels like owning a failure. So the safest move is silence. Green lights across the board, right up until everything is on fire.
What Real Accountability Looks Like
Maugham wrote for three to four hours every morning. Not because inspiration was guaranteed, but because he built the conditions for it to arrive. Accountability works the same way.
Real accountability means providing clarity. Actual clarity. On goals, roles and priorities. It means creating space for meaningful planning. Not the performative kind where everyone says enthusiastic yesses while their minds panic from the clear impossibility of delivery. The kind where a team honestly asks: what's going to get hard, and how will we handle it when it does?
It means building the psychological safety that lets teams actually live in the yellow.
Leaders need to receive yellow updates as an invitation for learning and collaboration. Show appreciation. Engage in the dialogue. Celebrate when yellow moments lead to better solutions.
Webinar
May
6
Retention Is a Communication Problem: New Data from 6,000+ Employees
This session gives leaders a clear diagnosis and practical path to treat retention as an infrastructure problem.
Register
Conference
Jun
2
Gartner Application Innovation & Business Solutions Summit Las Vegas 2026
Register
Webinar
On demand
Do Learning Programs Really Work? How to Turn Education Into Engagement In Healthcare
See how leaders are using learning programs to build trust with healthcare professionals and create measurable engagement.
Watch Now
Webinar
On demand
Fuel Your Front Line: Workforce Trends Shaping 2026
Get expert insight into the tools and tactics top frontline teams will need in 2026.
Watch Now
Webinar
On demand
Fix the Disconnect Between Projects and Profit
Your margins are hiding in disconnected data. Let's find them.
Watch Now
Webinar
On demand
AI in Customer Service: Faster Resolutions, Happier Customers
Don’t let rising demand burn out your team. See how to build a smarter, more resilient support org.
Watch Now
This requires the person raising yellow to do so constructively. They need to explore why things aren't going according to plan and offer insight and strategic questions. No finger pointing. If there's a performance problem, that gets addressed privately.
But when someone raises a legitimate concern early, that's exactly what you want. It's the difference between two kinds of questions after something goes wrong.
One kind sounds like: Who dropped this? Why wasn't this caught? Whose responsibility was this?
The other sounds like: What are we learning? Where are we stuck? How can we all help?
The first assigns shame. The second builds a team that tells you the truth. And a team that tells you the truth catches problems while they're still solvable.
Stop Waiting for Things to Break
To leaders who keep finding themselves asking "who's accountable" after things go wrong: What if the question itself is the evidence? Evidence that accountability was never built. That clarity wasn't provided. That planning was performative. That safety was absent.
The instinct when something breaks is to find the failure point and fix it. That feels like rigor. But it's the equivalent of waiting for inspiration to strike and then asking why it didn't show up sooner.
The failure you're seeing isn't a team problem. It's a setup problem. And the accountability you're looking for after the fact is the very thing that was missing before it.
Stop waiting for things to go wrong to invoke accountability. Start building it before they do.
Editor's Note: What else keep projects on track and collaboration flowing?
- The Daily Behaviors That Transform Good Teams Into Great Ones — The path from functional to exceptional teams isn't mysterious. Most have the talent they need. What they lack are daily behaviors that create cohesion.
- Mastering the Art of Getting Started: 3 Tips to Overcome Decision Paralysis — Projects can get derailed before they even get off the ground. Here are four tips to overcome the odds and move past decision paralysis.
- The Blurring Lines Between Collaboration and Project Management Software — Today's project management tools don't just track work, they do it. But is “work management” a leap forward or another layer of digital noise?
Learn how you can join our contributor community.