Skip to content

2022

  • 2 min read

Staying Ahead of the Curve

Keeping pace with technology is no longer optional — it’s essential.
The ThoughtWorks Technology Radar is one of the best tools for tracking emerging trends and staying informed about what matters most in the fast-changing tech landscape.

For architects and tech leaders, it’s not just a reading list — it’s a strategic compass.

The Value of the Radar

The Technology Radar provides a structured view of the tools, techniques, platforms, and languages shaping modern software.
It’s organized into four key rings — each representing a different stage of adoption and confidence:

  • Adopt — Technologies mature and proven enough for production use.
    Stable, well-tested, and delivering real business value.
  • Trial — Promising approaches worth exploring in limited pilots.
    May involve some risk but strong potential rewards.
  • Assess — Technologies to watch and evaluate.
    Not yet validated, but relevant to your strategic horizon.
  • Hold — Items that are either outdated, overly risky, or not recommended.
    Often useful reminders of what to avoid or phase out.

This simple framework helps organizations prioritize exploration and investment while avoiding unnecessary hype.

Making It Useful

A radar is only as valuable as the conversations it sparks.
The real power lies in shared situational awareness — aligning teams on what’s relevant, what’s emerging, and what’s ready to retire.

When used well, a tech radar helps: - Connect technology decisions with business strategy.
- Encourage continuous learning and experimentation.
- Prevent tech sprawl and redundant exploration.
- Identify capability gaps early.

A good radar doesn’t predict the future — it prepares you for it.

Build Your Own

Every organization’s context is unique.
That’s why ThoughtWorks encourages teams to create their own radar, tailored to their strategy, architecture, and culture.

Creating an internal radar fosters ownership and collaboration.
It makes technology direction visible, trackable, and open to discussion.

Final Thoughts

The best technology organizations don’t just react to change — they anticipate it.
Using a radar builds the muscle memory to keep learning and adapting, together.

So whether you follow the ThoughtWorks Radar, Zalando’s model, or your own internal version — make it a living artifact.
Revisit it regularly. Discuss it openly. Let it shape your choices.

Staying ahead of the curve isn’t about guessing what’s next —
it’s about creating the habit of paying attention.

  • 2 min read

Optimize for Speed and Deploy with Confidence

Performance metrics are the backbone of modern software delivery.
They tell you not only how fast your teams move, but how safely they can do so.

Without metrics, improvement is guesswork.
With the right ones, you gain clarity, focus, and the ability to continuously refine how software flows from commit to customer.

The Four Key Metrics

The DORA metrics, popularized through Google’s State of DevOps reports, have become the gold standard for measuring software delivery performance:

1. Deployment Frequency

How often can your team release changes into production?
Frequent deployments signal smaller, safer releases and a healthy CI/CD pipeline.

2. Lead Time for Changes

How long does it take a commit to reach production?
Shorter lead times indicate smoother flow and fewer bottlenecks between development and deployment.

3. Change Failure Rate

What percentage of deployments result in incidents or rollbacks?
A lower failure rate reflects stronger quality practices, better testing, and improved confidence in delivery.

4. Time to Restore Service

When something breaks, how long does it take to recover?
Fast recovery time demonstrates resilience and effective incident response.

Together, these four metrics help you evaluate both speed and stability — the twin pillars of modern DevOps performance.

Why They Matter

These measures don’t just quantify output — they shape culture.
When teams track and discuss them openly, they start to see delivery as a shared responsibility.

It shifts the mindset from:

“How do I finish my task?”
to
“How do we deliver value safely and continuously?”

That’s how elite DevOps organizations emerge — through visibility, trust, and measurable improvement.

Ready to Benchmark Yourself?

Google offers an excellent quick self-assessment to help you gauge your current capabilities:
➡️ DevOps Quick Check

You can also dive deeper into their insights on delivery performance and team organization:
- 📘 2022 State of DevOps Report
- 🧭 Organizing High-Performance Teams

Final Thoughts

Optimizing for speed isn’t about moving recklessly fast — it’s about delivering with confidence.
When you track these metrics consistently, they become feedback loops that drive improvement across the entire lifecycle.

Measure what matters, improve what you can, and celebrate every iteration forward.

  • 3 min read

Gardening Teamwork

Growing up on a soccer field taught me lessons that still shape how I view teamwork and leadership today.
From dedication to collaboration, the mindset needed to win on the pitch isn’t so different from what’s needed to succeed in system development.

Both require strategy, trust, communication — and the ability to adapt together.

Teamwork and Shared Goals

In soccer, a team is made up of players with different roles, but one shared goal.
The same applies to system development — architects, designers, developers, testers, and product owners all bring unique skills to achieve a common outcome.

The best moments, both on the field and in tech, happen when a group moves in sync — covering for each other, playing to each other’s strengths, and striving for the same win.

“Great teams are not made up of many well-rounded players. Great teams are made up of a variety of players, each having their own strengths.” — Pelé

Guiding Principles and Strategy

Just like a soccer team has a game plan, development teams need strategy and guiding principles.
A good game plan connects every move to purpose — ensuring each sprint or release supports a bigger goal.

In both fields, clear communication is the lifeblood.
Without it, coordination breaks down, trust fades, and the whole system suffers.

Building Trust Through Clarity

Trust grows when expectations are clear.
Everyone should understand the vision, goals, and responsibilities of the team.
This creates alignment — and allows people to step up, take initiative, and support one another.

A culture of open communication and risk-taking is essential.
Encourage honesty, curiosity, and the courage to try new ideas.

Autonomy, Mastery, and Purpose

Teams thrive when they experience these three conditions:

Autonomy

Freedom to make decisions within clear boundaries.
Ownership over how work is done — whether on the field or in product delivery.

Mastery

The drive to improve and grow in a specific craft.
Mastery brings pride, competence, and continuous improvement.

Purpose

Connection to something larger than yourself — a mission, product, or shared vision.
Purpose fuels motivation and resilience through challenges.

These principles, highlighted by Daniel Pink and others, apply everywhere — from engineering to sports to leadership.

Architecture and Bounded Contexts

In soccer, the white lines define the playing field — the bounded context.
The same concept applies in software and organizational design.
Clear boundaries foster autonomy without chaos.

Organizing teams around business domains allows them to act independently and make faster, more focused decisions — reducing dependencies and friction.

“You build it, you run it.” — Werner Vogels, Amazon CTO

Conway’s Law reminds us that how we structure teams shapes the systems we build.
If communication lines are rigid and centralized, our software will reflect that — with tight coupling, bottlenecks, and friction.

Lessons from the Field

Success in soccer is measured in games.
Success in system development is measured over time — in adaptability, quality, and impact.

But the lesson is the same: Stay resilient. Work together. Keep improving.

Try building teams small enough to share two pizzas.
Organize them around bounded contexts, give them autonomy, mastery, and purpose — and coach them with clarity and trust.
That’s where the magic happens — both on the pitch and in product delivery.

“Great teams are gardens — they need space, light, and time to grow.”

  • 2 min read

How Guardrails Empower Teams

In a fast-changing world, teams need more than freedom — they need clarity.
Well-defined guardrails give direction without restricting creativity.
They help people make confident decisions, align with shared goals, and innovate safely.

Guardrails aren’t fences. They’re guiding principles and vision anchors that empower teams to move faster — not because they’re controlled, but because they know where they’re headed.

Why Guardrails Matter

Every empowered team operates within a shared purpose.
When that purpose is clear and supported by guiding principles, alignment becomes natural — not enforced.

Guardrails: - Encourage autonomy while maintaining direction.
- Reduce hesitation by defining what “good” looks like.
- Strengthen trust between teams and leadership.
- Enable faster, more confident decisions.

When teams know the boundaries, they no longer need to ask permission for every step — they can focus on progress.

Defining Your Guiding Principles

Every team is unique.
That’s why principles should reflect your culture, strengths, and goals — not generic slogans.

Start by asking: - What values define how we work together?
- What outcomes matter most to our customers?
- What are the non-negotiables that guide our decisions?

Use these to shape your principles — short, memorable, and actionable.
They should make decisions easier, not harder.

“Guardrails don’t restrict freedom — they protect momentum.”

Vision as a North Star

A vision statement ties your principles together.
It tells everyone not just what you’re building, but why it matters.

Communicate it frequently — not just when things go wrong.
Reinforce it when things go right.
A strong vision doesn’t just align work; it inspires it.

How Guardrails Enable Creativity

It might sound counterintuitive — but constraints can increase creativity.
When people know the boundaries, they can focus their energy on innovation within safe parameters.

Guardrails: - Define the field, not the moves.
- Encourage experimentation that aligns with strategy.
- Make it easier to recover from mistakes, because risk is already managed.

This kind of structure builds psychological safety, where people can challenge ideas, share feedback, and try new things without fear.

Building and Maintaining Them

  1. Co-create your principles with the team.
    Involve everyone in defining what matters — ownership builds commitment.
  2. Keep them visible.
    Add them to your onboarding, sprint planning, retrospectives, and dashboards.
  3. Revisit regularly.
    As teams and products evolve, your guardrails should too.
  4. Model them in leadership.
    Teams follow behavior, not documents. Live the principles you define.

The Goal: Freedom Within Direction

The balance between autonomy and alignment defines great organizations.
With strong guardrails, teams can act quickly, innovate boldly, and stay true to shared goals.

“Empowered teams don’t need permission — they need purpose.”

So let’s use guardrails not as limits, but as tools for success.
They keep us focused, aligned, and confident — while giving every team the space to grow and create.

  • 1 min read

Finding the Right Angle

Addressing a problem can be tricky.
The key often lies in finding the right angle — the perspective that reveals what truly matters.

Effective problem solving requires the ability to zoom in and out.

Zoom In

When you zoom in, you focus on the specific aspect of a problem and its immediate context.
You define the scope, understand constraints, and clarify what needs to be achieved.
This view helps when you’re designing a concrete solution, refining implementation details, or resolving an isolated issue.

Zoom Out

Once the local context is clear, zooming out allows you to see the broader system — how things connect, overlap, and depend on each other.
It reveals friction points, patterns, and opportunities for alignment or optimization.
From this higher perspective, you can adjust priorities and design with long-term resilience in mind.

The Dual Perspective

The real power comes from combining both views:
- Zoom in for precision and execution.
- Zoom out for strategy and sustainability.

Switching between these perspectives enables smarter, more adaptive decisions — turning complexity into clarity.

Architecture, like photography, is about framing the right shot — finding the angle that brings focus to what truly matters.