Leo blinked. "Well… the spec said 'short-lived token,' but it didn't define 'short-lived.' I guessed."
When something goes wrong, avoid the blame spiral. Follow Jana M.’s method—facts, curious questions, and a tiny actionable fix—and you’ll solve problems faster while keeping your team intact.
Leo, the junior developer responsible for the broken authentication module, slumped in his chair. "I don't know what happened," he muttered. "I followed the specs." jana m
"Let me show you something," Jana said softly.
The Feedback Loop
Priya watched, impressed. Within a week, the Nova update was back on track. But more importantly, the team started a "Jana M. Rule" of their own: before blaming anyone, they’d run the three steps.
"Ah," Jana nodded. "That’s on us, not you." Then, step three: "Small immediate fix—let’s update the spec to say '1800 seconds,' and you add a comment in the code explaining why. Deal?" Leo blinked
Leo’s shoulders relaxed. "Deal."
Priya, the team lead, was about to launch into a post-mortem. But Jana M. raised a hand. Leo, the junior developer responsible for the broken
Jana M. was known around the office for two things: her color-coded project boards and her quiet habit of listening twice as much as she spoke. When the "Nova" update fell two weeks behind schedule, the tension in the daily stand-up was thick enough to cut.
