liveBook · Manning

Strategy

A strategy is a planned approach for achieving objectives through coordinated choices, priorities, and actions.

How 3 Manning books explain it

Architecture Modernization: Socio-technical alignment of software, strategy, and structure

A modernization strategy is a planned approach for updating software architecture, technology, and organizational capabilities to achieve defined business objectives.

How it is used
Connects architecture modernization investments to business outcomes and gives stakeholders a shared basis for prioritization.
How deep it goes
Works through portfolio and subdomain choices, then addresses roadmaps and adaptation rather than prescribing implementation details.
Examples
Contrasts freight optimization and live arrival times with invoicing, and considers moving a coupled monolith before modernizing its subdomains.
What you can do after
Practice/perform portfolio prioritization, select proportionate subdomain approaches, and revise an outcome-led roadmap as evidence arrives.

Read how Architecture Modernization: Socio-technical alignment of software, strategy, and structure explains strategy →

Claude at Work

A strategy plan is a high-level plan describing the overall approach for delivering a software feature or initiative.

How it is used
Sets the overall approach for a feature before delivery and implementation planning.
How deep it goes
Works through strategy creation and handoff, while leaving task decomposition and implementation detail to subsequent plans.
Examples
Uses a core messaging feature with browser-based chat and a delivery plan of reviewable vertical slices.
What you can do after
Apply it via Claude Code to establish an approach, save the plan, and hand it off for reviewable delivery planning.

Read how Claude at Work explains strategy →

Think Like a Software Engineering Manager

A strategy is a coordinated plan for achieving defined goals and realizing a desired direction.

How it is used
Coordinates team goals, organizational priorities, execution choices, and adaptation when expectations or conditions change.
How deep it goes
Explains strategy through goals, vision, metrics, road maps, implementation choices, dependencies, risks, stakeholders, and communication.
Examples
Uses team planning, phased software upgrades, competitor-driven pivots, attrition planning, and Microsoft’s cloud-first shift.
What you can do after
Build it from scratch by aligning priorities, defining success, choosing an execution approach, and planning communication and mitigation.

Read how Think Like a Software Engineering Manager explains strategy →

Also covered in

What to know first

Related concepts

Questions about strategy

What is strategy?

A strategy is a planned approach for achieving objectives through coordinated choices, priorities, and actions.

Which Manning books explain strategy?

Architecture Modernization: Socio-technical alignment of software, strategy, and structure, Claude at Work and Think Like a Software Engineering Manager.

What should I know before learning strategy?

Manning books that teach strategy usually introduce goal, CEO, organizational vision and risk first.

What kinds of strategy are there?

Kinds of strategy include product development, total modernization and acceptance testing strategy.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.