In any fast-growing company, decision-making speed can make or break momentum. But what happens when too many decisions get funnelled through a handful of leaders? Things slow down — and nobody wins.
Lately, I’ve been thinking about how we can get out of the way and let our developers take more ownership over the small but important decisions they’re more than capable of making. Not only does this help us move faster, but it also creates a team culture where people feel trusted, valued, and engaged.
The Problem: Too Many Questions, Not Enough Action
It all started when I noticed developers were asking basic questions that they absolutely knew the answers to.
For example, we had a map button on a map page that literally took users back to the same map page. A developer asked, “Should we remove this??”
I mean… of course! That button served no purpose. It was an obvious fix. But the fact that the dev felt the need to ask told me something bigger:
– They weren’t unsure about the decision.
– They were unsure if they were allowed to make it.
That’s when it hit me — we accidentally created a culture where developers didn’t feel like they could make even the simplest UX decisions without checking with design or product leadership first.
And that was a problem.
Changing the Culture: Encouraging Developers to Take Ownership
If we want to keep moving fast, we can’t afford to micromanage every decision. Instead, we need to trust our team to make good calls and act quickly — knowing that if something goes wrong, we’ll just fix it.
After all, we’re not running an ICU. No one’s going to die if a button is removed or a layout is slightly off. Real estate tech is not life or death.
So, we started making a conscious effort to empower developers — especially senior ones — to make decisions without waiting for approval.
It’s not about throwing structure out the window. It’s about recognizing that:
— Most small decisions don’t need a meeting.
— A 90% correct decision today is better than a 100% perfect decision next week.
— Fixing a mistake is often faster than waiting for approval.
Early Results: Who Steps Up, Stands Out
We’re still early in this shift, but one thing is clear:
The people who act fast and take ownership are getting noticed.
They’re getting:
— More visibility
— More trust
— More opportunities to lead bigger projects
Because when you show that you can make decisions and keep things moving, people naturally start relying on you more.
And the best part? It’s working.
We’re seeing fewer unnecessary questions, more confidence in decision-making, and faster progress on projects.
What Happens When a Mistake is Made?
No big deal. We fix it and move on.
Of course, for bigger changes that need more input, we still collaborate as a team. This isn’t about making random rogue decisions — it’s about eliminating unnecessary roadblocks.
The difference? Developers now feel empowered to make calls on things they already know make sense.
How We’re Reinforcing This Culture
We’re making sure this isn’t just a one-time conversation, but an ongoing shift in how we work. Here’s how:
- Public Recognition
- In our Zoocasa daily stand-ups, when someone makes a great decision on their own, we give a big thank you.
- We make it clear: this is encouraged and valued.
2. Clear Expectations
- We’re not asking devs to solve major UX or product strategy issues solo.
- But for common-sense fixes? Go for it.
3. Fewer Approvals, More Action
- If something is low-risk and obviously better, just do it.
- If it’s a bigger change, loop in the right people, but don’t let process paralyze progress.
Final Thoughts: Why This Matters
This shift isn’t just about efficiency. It’s about culture.
When people feel trusted to make decisions, they don’t just work harder — they care more.
And when a team cares about what they’re building, great things happen.
If you’re noticing the same problem in your company, ask yourself:
- Are you slowing things down with too many approval steps?
- Do your devs hesitate to make decisions they clearly know are right?
- Could your team move faster if people felt more empowered?
If so, maybe it’s time to step back and let your team step up. 🚀
Let Developers Decide: How We’re Empowering Our Team to Move Faster was originally published in UX Planet on Medium, where people are continuing the conversation by highlighting and responding to this story.