Drop the methodology when it becomes the barrier

Drop the methodology when it becomes the barrier

When the methodology itself becomes intimidating or creates a power dynamic, abandon it. If event storming, domain storytelling, or any formal technique puts you on a pedestal while participants struggle, switch to whiteboards, boxes, and arrows—whatever helps people...
Drop the methodology when it becomes the barrier

Revisit Decisions When Context Changes

Decisions are made based on the context at a specific point in time, such as team size or available technology. Documenting this original context allows you to determine if it has changed enough to justify revisiting the decision. This prevents historical choices from...
Drop the methodology when it becomes the barrier

Address Dissent by Enabling Commitment

After a decision is made, allow dissenting members to express their concerns freely without becoming defensive. Then, shift the conversation by asking, “What do you need to go along with this decision?” This validates their perspective while focusing on a constructive...
Drop the methodology when it becomes the barrier

Retroactively Document Foundational Decisions

Reverse-engineer Architecture Decision Records (ADRs) for foundational decisions that were never formally documented. This makes implicit constraints explicit, clarifies historical context, and allows the team to re-evaluate them. It provides a clear baseline for new...