Engineering Strategy

A set of strategic patterns on addressing business capabilities with a monolith and microservices approach.

A set of business tools and patterns from an engineering point of view.

How is the role of the staff engineer and how this role addresses the engineering strategy.

A high-level book on business strategy, people, culture, data and architecture and how this drives cloud velocity.

A set of wardley maps on IT. Bringing situational awareness to different contexts.

Understand the core components of a strategy.

Using Wardley Mapping and other sensemaking approaches to help organizations anticipate market changes and user needs.

Team Topologies is a practical, step-by-step, adaptive model for organizational design and team interaction based on four fundamental team types and three team interaction patterns.

An essential introduction into system thinking. It helps the reader to understand the fundamentals and introduces several system traps and how to overcome them.

Strategic patterns to understand complex domains and how to model them based on the impact on the business competitive advantage.

An implementation approach to DDD from strategic patterns to tactical patterns with code examples.

An accessible book to learn the main concepts of Domain-Driven Design.

A deep explanation of the origin of Wardley Maps up to the full understanding of how to do strategy which it is adaptive to the environment.

Concrete tools, techniques, and processes to align software architecture with your business domains, organizational design, team topologies, and corporate strategy.

A book about designing, building, deploying, and scaling a custom Internal Development Platforms (IDP).

How to build an engineering strategy from 0.

What's an engineering strategy.

A high-level guideline on defining a tech strategy.

In-depth reflection of what is a tech strategy.

Using wardley mapping to understand google appointments.

Introduction to what is a strategy for tech.

Describes strategic architectural initiatives, a framework which allowing product peeps and techies to make progress on big technical improvements via aligned autonomy.

Introduces what an architecture decision record is, describes the terminology, how to document the finalized architecture, and focuses on the best practices by presenting real scenerio.

Building a common language for vision, mission, goals, objectives, roadmap, plans, milestones, policies.

First in a series of posts about strategy why, how and what.

A guide on how to write and document an engineering strategy.

Explains how AMET coordinates and upskills all teams and stakeholders in the modernization initiative.

Using Cynefin Framework, it shares in which domains designing an engineering strategy makes more sense compared to just execute.

How platforms emerge from business challenges and the different types of teams like enabling and platform teams collaborate with stream-aligned teams to create the space and opportunities for platforms to evolve.

When a stream-aligned team starts supporting internal customers and acting as an interim platform team. How to deliver a great internal experience while delivering features for external clients.

Eleven prevalent strategic directions that organisations traverse with examples.

A unified theory of Engineering strategy, with a particular emphasis on how you can drive strategy.

How to apply organization engineering strategy to the local context while keeping aligned with organization goals.

A collection of links on the topic gathered.

A comparison of chess and poker games and how they relate to engineering strategy.

Culture guides and constrains your strategy. Using strategy to influence your culture.

Multi-part strategy guide with specific templates you can deploy rapidly in your organization.

How to combine an engineering strategy with the north star framework to be guided by actionable metrics.

How only investing on good and best engineering practices won't position your company ahead of the competition that makes context specific decisions.

A set of relevant aspects of the business that help people to have a broader understanding to improve their engineering strategy with a set of questions to ask to the domain experts.

How the basal cost, composed of direct impact on team capacity of the added complexity and the cost of the development or evolution of other features, affects the existing systems and teams to deliver value.

An engineering strategy example of how to deal with teams with competing priorities.

How Cat has used Wardley Maps to inform her always evolving strategy for the modernization of Ticketmaster’s core ticketing platform not only in terms of technical capabilities and architecture but also process maturity, organizational design, and more.

Simon Wardley examines the issue of situational awareness and explains how it applies to technology.

How to understand and categorize domains into ordered, complicated, complex, and chaotic, and how to navigate them.

Understand how communication within an organization creates patterns that repeat themselves and scale up to the organization.

How to understand the present to design a better present that will create better futures from a system thinking perspective.

An approach combining the essentials of Wardley Mapping with Team Topologies with a strong focus on user needs.

An online course to introduce people into Wardley Mapping.

Hands-on exercises show you how to use DDD strategic and tactical design in your implementations.

Combining Wardley Mapping, DDD & Team Topologies, this workshop will help you to design for adaptability.

Introduction to engineering strategy theory and components.

This masterclass builds on our work with software, system and enterprise architects and product, program and executive managers including CTOs and CIOs.

A template with the core elements of an engineering strategy, the high-stake problem, the understanding phase, the direction, and coherent actions.

Visualize the contract between bounded contexts and teams with a collection of patterns.

Help you to visualise the strategic importance of each (sub)domain or business capability in your architecture allowing you to make business model-aligned architectural decisions.

Prove product market fit with an MVP.

Complete GitLab three-year strategy. Containing direction, customer focus, and team dynamics.

Flutter annual strategy document for 2022.

Gitpod purpose, vision, and strategy.

An engineering strategy when the product verifies product market fit and the engineering isn't evolving the practices to match the new product needs.

An engineering strategy to enable fast experimentation during the onboarding for a B2C application.

Discord community focused on Engineering Strategy.

Engineering strategy interviews to tech leaders in English and Spanish by Aleix Morgadas.

A podcast by Henry Suryawirawan where experienced technical leaders share the often undefined, beyond-the-code skills that shaped their journeys.