Skip to main content

Joern Buchwald

Independent Consultant

I help organizations fix their software engineering culture

Software engineering needs collective alignment within and across development teams and stakeholders. Organizational culture shapes how effectively that works.

For many organizations, culture may become a critical bottleneck to their AI transformation. Without alignment, AI adoption can backfire and amplify organizational dysfunction instead of improving development as a whole.

Signs your engineering culture needs attention:

  • 🧨 Growing technical debt
  • 🤷‍♂️ Blurred ownership and accountability
  • 🗺️ Architectural drift
  • 😒 Low trust between engineering and leadership
  • 🎓 Lack of knowledge transfer and learning
  • 🤖 Polarization about AI adoption
  • 🪫 Frustration, burnout and cynicism

The deeper systemic issue behind these symptoms is a lack of coherence between different perspectives. Leaders and developers, both within and across teams, struggle to develop a shared mindset of how to engineer software sustainably by balancing engineering practices and business constraints. As a result, everyone gets frustrated and settles for suboptimal outcomes.

The key to a strong software engineering culture is to address the underlying psychological barriers: People need to work within psychologically safe, dependable and clear structures in which they have a perceivable impact on something meaningful to them. When these conditions are met, people are more likely to develop a sense of ownership, intrinsic motivation and an openness to a shared engineering mindset.

But do existing structures and workflows cultivate or sabotage these conditions?

As an independent consultant, I help organizations diagnose and fix these underlying culture issues. I combine 10 years of hands-on engineering experience across frontend, backend and infrastructure with expertise in systems thinking and psychology.

I help my clients make sense of the psychology behind various aspects of software engineering:

🗺️ Technical Boundaries​

Do engineers have a shared understanding of all the technical building blocks so that they can make architecture decisions on behalf of their team?

👥 Team Topology​

Are team boundaries, responsibilities and interaction workflows between teams clearly defined?

🧨 Hidden Quality Risks​

Do engineers and non-technical stakeholders have a shared understanding of software quality risks and their need for proactive mitigation?

🔁 Continuous Delivery Feedback Loop​

Are development teams included in the full feedback loop from planning to running their code in production?

🗓️ Software Planning​

What are the meaningful promises made to stakeholders and where is the tradeoff between trust and planning bureaucracy?

🧠 Human Learning​

Is it a collective responsibility to teach and acquire knowledge within and across teams?

Interested? Read more or contact me.