Project Management
What If You Treated Change Resistance Like a Design Problem?
A change-management hackathon replaces abstract debate with a small, testable intervention around one stubborn workflow.
Choose one adoption barrier, bring the people who experience it, prototype a low-risk intervention, and measure behavior before scaling the solution.
The project team celebrates go-live. Two weeks later, employees are still updating the spreadsheet they were meant to retire. Leaders call it resistance, send another reminder, and schedule training. The spreadsheet remains undefeated. The August 7 change-management hackathon offers a better mental model: bring a real challenge and work on it collaboratively. Instead of treating people as the obstacle, investigate the friction. Perhaps the new system hides information needed for a morning meeting, asks for data nobody owns, or turns a two-minute task into seven clicks and a small emotional journey.
Define one observable behavior, not a broad ambition. ‘Managers approve requests in the new system within 24 hours’ is useful; ‘embrace transformation’ is not. Invite users, process owners, technical support, policy owners, and one decision-maker. Map the current moment of friction, gather evidence, and generate several small interventions: remove a field, change the trigger, add an example, adjust permissions, or redesign the handoff. Pick the safest high-value test and run it with a small group. A hackathon should not become a colorful workshop where sticky notes achieve adoption on behalf of humans.
Set a short test period and compare completion, cycle time, error, support demand, and user confidence with the previous process. Ask what people did, not merely whether they liked the session. Keep safeguards for privacy, compliance, and operational continuity. If the intervention works, document why and scale it in stages; if not, preserve the learning and change the hypothesis. Project leaders should maintain an adoption backlog alongside the technical backlog. Change is not a communication package attached to delivery. It is part of the product, and users reveal its defects by the routes they take around it.