My thumb is currently hovering over a pixelated blue icon that looks like it was drawn in a fever dream back in 2003. It’s supposed to be the ‘Upload’ button for Project Phoenix, our company’s homegrown project management suite, but every time I click it, the browser refreshes and my attachment vanishes into the digital ether. I’ve spent precisely 13 minutes trying to share a single PDF.
In the time it took for the spinning wheel of death to mock me, I could have walked to the other side of the office, printed the document, and hand-delivered it while stopping to discuss the strange, waxy texture of an orange peel I just removed in one continuous spiral. But no, we are a ‘tech-forward’ organization, which apparently means we pay 43 developers to build a worse version of Jira because our CEO thinks our workflow is ‘too unique’ for off-the-shelf software.
The Arrogance of ‘Unique’
There is a specific kind of arrogance in believing your internal processes are so transcendent that they require a custom-built environment. It’s the Not Invented Here (NIH) syndrome, a corporate pathology that turns productive engineers into part-time maintenance crews for tools that shouldn’t exist.
‘If you build a bridge with a 3-degree incline, people will just swim.’
“
He’s right. When the internal tool is a friction-filled nightmare, the crowd doesn’t ‘adapt’ to the tool; they find a way around it. We don’t use Phoenix. We use Slack, we use Trello on personal accounts, and we use a sprawling mess of 103 different Google Sheets that are actually getting the job done while the official dashboard sits there, pristine and ignored, like a statue in a town no one visits.
The Ego of the Architect
Self-Sabotage: The Architect’s Trap
Coding a recycling logic gate.
Magnetic whiteboard solution.
I criticize the company for Phoenix, yet I fell into the same trap. We want to feel like architects when we should be focusing on being dwellers. In the corporate world, this manifests as resume-padding. An engineering lead realizes that ‘Migrated the team to Asana’ looks okay on a LinkedIn profile, but ‘Architected and deployed a proprietary enterprise resource planning system from the ground up’ looks like a ticket to a CTO role. So, they spend $1,003,000 of the company’s budget to build a tool that everyone hates, just so they can put a shiny new bullet point on their CV.
The Erosion of Morale
1,800,000+
Total Lost Minutes Annually (553 Employees)
If you have 553 employees losing even 13 minutes a day to a buggy internal interface, you aren’t just losing time; you’re eroding the collective morale. There is a psychological weight to using bad software. It makes you feel like the organization doesn’t value your focus. It tells the employee that their struggle with a broken ‘submit’ button is an acceptable sacrifice for the sake of the company’s ‘bespoke’ identity.
‘Environmental friction is the primary driver of silent quitting.’ People don’t leave because the work is hard; they leave because the tools are stupid.
“
They leave because they are tired of fighting the very systems meant to support them.
The Beauty of Reliable Materials
We often mistake ‘custom’ for ‘quality.’ Think about the physical space we inhabit. You want siding that has been engineered to last, like the high-performance materials from Slat Solution, which provide a reliable, aesthetic finish without the need for constant, bespoke tinkering.
If your project management tool requires a 43-page manual just to explain how to change a status, you haven’t built a tool; you’ve built a barrier.
The 93% Standard
The irony is that we think we are special. We tell ourselves that our ‘Agile-Waterfall hybrid’ or our ‘cross-functional pod structure’ is so revolutionary that no existing software could possibly capture its essence. It’s a lie. Your business is probably 93% the same as every other business in your sector. You have tasks, you have deadlines, you have budgets, and you have people who forget to check their email.
Focus on Shared 93% vs. Unique 7%
73%
By focusing on that unique 7%, you end up sabotaging the 93% that actually keeps the lights on. I’ve seen teams spend 113 hours debating the color-coding of a custom dashboard while their actual product launch was delayed because they couldn’t find the latest design assets in the ‘bespoke’ file system.
The Golden Anchor: Sunk Cost
Once a company has spent three years developing an internal tool, it becomes a holy relic. To admit it’s a failure is to admit that millions of dollars and thousands of hours were flushed down the toilet.
It’s like trying to fix a sinking ship by adding more heavy gold plating to the hull.
Bespoke is often just a synonym for broken.
They conduct mandatory training sessions where a chipper HR person tries to convince you that Phoenix is actually ‘fun’ to use.
The Winding Path of Good Intentions
I remember sitting in a meeting where Ben J.P. presented data on office navigation. The architects had built these beautiful, winding paths meant to encourage ‘spontaneous collaboration.’ The heat map, however, showed a straight, jagged line cut right through the middle of the grass and across the lobby. They didn’t want the experience the architect designed; they wanted to get their coffee and go back to work. Our internal software is that winding path.
We Should Be Brave Enough to Be Boring.
Buy the tool that works, use the siding that lasts, and focus our creative energy on the problems that actually matter to our customers. They care that we ship on time, not that we debug the ‘Upload’ button for the 43rd time.
The Final Submission
I finally gave up on Phoenix today. I dragged the PDF into a Slack DM and sent it to my manager. It took 3 seconds.
The ‘bespoke’ system is still spinning, still trying to authenticate my request, still trying to prove it’s special. I looked at the orange peel on my desk-one perfect, unbroken spiral. It’s a small masterpiece of natural engineering. It didn’t need a custom tool to be removed; it just needed a little bit of steady pressure and the right technique.
The best solutions let us eat the orange in one piece.
Maybe that’s the lesson. The best solutions aren’t the ones we build from scratch to satisfy our egos. The best solutions are the ones that let us get the peel off in one piece so we can finally just eat the orange.
The Final Question
Does your team actually like the tools you’ve built, or are they just polite enough not to tell you they’re swimming around your bridge?