[{"data":1,"prerenderedAt":72},["ShallowReactive",2],{"/blog/how-to-build-an-engineering-culture-where-develope":3},{"id":4,"title":5,"body":6,"date":59,"description":60,"extension":61,"image":62,"meta":63,"navigation":64,"path":65,"readTime":66,"seo":67,"seoTitle":68,"stem":69,"tag":70,"__hash__":71},"blog/blog/how-to-build-an-engineering-culture-where-develope.md","How to build an engineering culture where developers push back on bad specs instead of silently building the wrong thing",{"type":7,"value":8,"toc":55},"minimark",[9,13,16,19,22,25,28,31,34,37,40,43],[10,11,12],"p",{},"Silence is not agreement. It's often fear.",[10,14,15],{},"When a spec is vague, incomplete, or just wrong — developers usually know. But they build it anyway. And two sprints later, everyone's confused about why the feature doesn't fit.",[10,17,18],{},"This tends to happen when 𝗿𝗮𝗶𝘀𝗶𝗻𝗴 𝗮 𝗰𝗼𝗻𝗰𝗲𝗿𝗻 feels riskier than staying quiet. That's not a communication problem. It's a culture problem.",[10,20,21],{},"The fix isn't telling people to \"speak up more.\" That never works.",[10,23,24],{},"What works: make spec review a structured part of the process, not an optional moment before work starts.",[10,26,27],{},"One approach that changes the dynamic:",[10,29,30],{},"→ Assign one developer as spec owner per feature — not just executor\n→ Give them explicit permission to block work until questions are answered\n→ Treat unanswered spec questions as blockers, same as broken builds",[10,32,33],{},"When pushback has a formal channel, it stops feeling like insubordination and starts feeling like craft.",[10,35,36],{},"The cost of building the wrong thing is rarely just the sprint. It's the next sprint spent explaining it, reworking it, or shipping around it.",[10,38,39],{},"How do you create space for your team to challenge requirements before the work starts?",[41,42],"hr",{},[10,44,45],{},[46,47,48,49,54],"em",{},"If you want a remote dev team at VANTREXIS that challenges requirements before writing a single line of code, ",[50,51,53],"a",{"href":52},"/contact","Book a discovery call",".",{"title":56,"searchDepth":57,"depth":57,"links":58},"",2,[],"2026-05-01","Vague specs get built anyway when speaking up feels risky — structured spec ownership and formal review processes fix the root culture problem.","md","https://hcti.io/v1/image/019de21f-9b83-7bf9-a125-68e235c3c5e0",{},true,"/blog/how-to-build-an-engineering-culture-where-develope","2 min read",{"title":5,"description":60},"Engineering Culture: How Developers Push Back on Bad Specs","blog/how-to-build-an-engineering-culture-where-develope","Engineering Culture","l_WTGJypgnBWvD1qHKfIbYWfEB05615UGvf6hRcDSFY",1786649722029]