How can we improve developer experience and remove delivery bottlenecks?
Short answer
Find where engineers wait, repeat manual work or struggle to get reliable feedback. Follow a small change from idea to production and improve the biggest source of friction first. Developer experience includes tools, environments and CI/CD, but also clear priorities, useful reviews and access to the people who can make decisions.
Follow actual work through the system
Ask engineers to show a recent change, including the waiting. Look at setup, requirements, local testing, builds, reviews, deployment and operational feedback. A quick build does not help much if work then waits days for a decision.
Include new joiners and people working across team boundaries. Their experience often exposes assumptions that established team members have learned to work around.
Choose a constraint you can improve
- Unreliable environments: make the supported development path repeatable.
- Slow or noisy checks: separate useful feedback from checks people routinely ignore.
- Review queues: agree ownership and keep changes small enough to review.
- Manual releases: reduce repeated steps and make recovery understandable.
- Unclear priorities: give people a decision owner and a stable definition of the outcome.
Compare the team’s experience and elapsed time before and after. Do not interpret time saved as an automatic promise of proportionally more features.
Support engineers and their leaders
I work directly with engineers on CI/CD and feedback loops, and coach leaders on the priorities and relationships that shape delivery. At Remo my work included CI/CD and operational resilience; elsewhere the first useful intervention may be a leadership decision rather than a new tool.
Related questions
Do we need a platform team?
Start with the repeated needs and their scale. A small shared improvement may be enough; a dedicated team only helps when its remit and users are clear.
How do we know the changes helped?
Combine engineer feedback with evidence from the workflow: less waiting, fewer failed checks, easier setup or more dependable releases. Check that customer outcomes and quality remain sound.