Key Takeaways
Use Strategic Doing to turn networked assets into adaptive action
Strategy must fit the network. Traditional planning assumes that a small group can analyze a stable environment, decide what to do, and direct others to carry it out. But many modern challenges cross organizations, shift quickly, and involve people no one can command. Strategic Doing is an iterative way to build strategy through collaboration: make progress with available resources, learn from action, and adjust as circumstances change. The authors developed it through work in places such as Oklahoma City, where a small civic team helped catalyze $403 million in additional private investment by 2000.
Adaptation beats prediction. The book uses the S-Curve to show how an innovation or organization grows, levels off, and declines. Waiting for certainty can leave a group stranded on the downward slope. Networks need a repeatable way to move resources toward new opportunities.
What's striking is the shift from treating strategy as a document to treating it as an organizational capability. That aligns with learning-oriented approaches in fields such as software development, where short cycles expose errors before they become expensive. The network lens also explains why a plan can be logically sound yet inert: participants may not share authority, incentives, or a reason to act. The case for iteration is strongest when conditions are uncertain. In stable, tightly regulated work, however, predictability and standard procedures remain valuable. Strategic Doing is best understood as a complement to those tools, not a universal substitute.
Make meetings safe, focused, and small enough for every voice
Conversation is designed. Complex collaboration starts with the conditions for honest discussion. Choose a neutral place when no partner should have home-field advantage, remove distractions, and agree on basic rules of respect. Research cited in the book associates more substantive conversation with greater well-being, while interruption studies suggest it can take substantial time to regain focus after a disruption. Group size matters too: the authors point to research favoring small teams, often around five to seven people, for complex work.
Safety changes participation. In Flint, a community meeting opened with participants discarding their business cards, signaling that every person had something to contribute, regardless of title or status. The practice reflects psychological safety, a shared sense that people can take interpersonal risks without being punished or dismissed. The group also aims for equity of voice, so the loudest participant does not become the default leader.
Psychological safety is not the same as comfort or consensus. It is the permission to question assumptions, admit uncertainty, and offer dissent without being humiliated. That distinction matters because a pleasant meeting can still exclude inconvenient perspectives. Neutral venues and explicit norms can lower status signals, but they cannot erase power differences, especially when some participants control money, jobs, or access. Facilitators therefore need to notice not only who speaks, but whose ideas receive attention and become decisions. Small groups support depth, while larger networks may still be necessary to bring in the expertise and legitimacy that a small working team lacks.
Ask questions that invite possibilities, not endless diagnosis
The question sets direction. A technical question has a known problem and a relatively clear solution. An adaptive question has no single answer and requires people to test possibilities together. For adaptive challenges, the book recommends appreciative questions, which focus attention on strengths, successful moments, and opportunities rather than dwelling indefinitely on deficits. This approach draws on Appreciative Inquiry, a method for helping groups imagine and develop what they want more of.
Reframing can unlock ideas. The book recounts how Edwin Land began imagining instant photography after his young daughter wondered why a picture could not be seen immediately. A different question opened a new design space. Similarly, a botanical garden board moved from worrying about low attendance and costs to considering how more people could experience its beauty. Questions phrased as how something might be done invite possibilities without prematurely judging whether it can or should be done.
A well-chosen question acts like a search strategy: it determines which evidence people notice and which options they consider. This is compatible with research on attention and problem framing, where changing the representation of a problem can change the solutions people generate. The appreciative approach is especially useful when a group is stuck in repetitive blame. It should not become forced optimism, though. Naming harm, failure, and unequal conditions is sometimes essential, particularly in public health or community work. The practical distinction is between examining problems to learn what matters and treating diagnosis itself as progress.
Inventory what people can contribute, then recombine the pieces
Start with available assets. An asset is a resource that could help move a group toward an outcome. The book asks teams to look beyond money and consider physical resources, skills and knowledge, social connections, and financial or in-kind support. A resource counts only when participants can actually access it, its owner agrees to share it, and the group can describe a plausible use. This shifts attention away from waiting for grants or permission and toward what is actionable now.
Connections create new value. In one manufacturing workforce project, a participant's interest in sustainability and experience in curriculum design helped inspire a new worker certification. In Milwaukee, businesses and researchers connected separate water-related capabilities, helping establish a freshwater technology hub. These examples illustrate recombinant innovation: combining familiar elements in a new configuration. The point is not to force every resource into a solution, but to help people notice useful links across professional and organizational boundaries.
Asset mapping makes hidden capacity visible, and it can correct the tendency of organizations to define themselves by budget lines or departmental boundaries. It also resembles recombination in evolutionary biology: variation already present in a system can produce novelty when elements interact in new ways. Yet an asset-based lens has a limit. It can sound as if creativity alone overcomes material deprivation, or as if communities should solve structural problems without outside investment. The book's strongest claim is narrower and more useful: available resources can create a starting point, not necessarily a complete solution. Good facilitation also respects that people may choose not to contribute an asset.
Choose the high-impact move your group can actually start
Make prioritization visible. When a group has many ideas, the Big Easy method compares each option on two dimensions: potential impact and ease of implementation. A simple 2 by 2 matrix lets participants place options on the same visual field and makes their judgments discussable. It is not a promise that the selected option is perfect. It is a way to choose a promising first move without pretending that complex decisions can be reduced to precise calculations.
Early wins build confidence. One downtown group chose planters as its first beautification project, even though outsiders thought the idea too modest. The project gave members practical work to share and helped attract wider interest. In southern Indiana, local organizers chose a maple syrup festival over a stalled plan to convert an outlet mall into an agricultural hub. The festival began within 15 months and helped bring visitors and new business activity to the area.
The matrix is valuable partly because it externalizes disagreement. Instead of debating vague preferences, participants can see whether they differ over impact, feasibility, or both. This resembles multi-criteria decision methods, but the simplified tool is easier to use when information is incomplete. Its weakness is that groups can mistake a visual consensus for objective truth. Ease may reflect existing privilege, and impact may be judged differently by people who bear different costs. A strong facilitator asks whose definition of impact is being used and treats the ranking as a provisional choice that can be revised after evidence arrives.
Define success so concretely that partners can recognize it
Turn aspiration into a shared picture. Vague goals sound agreeable but can conceal incompatible assumptions. The authors suggest asking what success would look like, what people would feel, and whose lives would change. Their kitchen example shows why: partners who disagreed about style discovered that they wanted a room where friends gathered, food was shared, and cleanup was easy. Describing the intended experience revealed a common outcome that neither person's first description captured.
Use measures to clarify meaning. If a school group wants students to be excited to attend, absenteeism might be one indicator to consider. At this stage, a measure is a shared definition, not necessarily a commitment to build a formal evaluation system. In a workforce initiative in Indiana, teams set their own measures and funding was released in stages as projects developed. The program exceeded its targets and reported that 80 percent of initiatives remained active two years after the grant ended.
Specific outcomes function as coordination devices. They let partners compare interpretations before those differences turn into implementation conflicts. The book's distinction between clarifying a measure and imposing a performance target is important: measurement can support shared understanding, but targets can also narrow attention toward what is easiest to count. In education, for instance, attendance may reflect engagement, but it can also reflect transportation, health, or family conditions. A useful measure should illuminate the intended outcome without pretending to capture all of it. Qualitative descriptions and quantitative indicators are most informative when they correct one another.
Treat the first project as an experiment, not a miniature master plan
Action produces knowledge. When a challenge is complex, no team can fully predict how the system will respond. The book draws on the idea of small wins: break an overwhelming problem into manageable steps that provide evidence and keep people engaged. A starting project should be limited in scope, involve everyone, test an assumption, create visible progress, and avoid requiring permission that could stall the work. The authors suggest that 90 to 120 days is often a useful duration.
Scale what teaches you. In a national engineering education initiative, teams at 50 universities launched more than 500 small projects, from course modules to makerspaces. Some led to larger programs and institutional support. Others offered lessons without becoming permanent. The point was not to build a grand plan in miniature, but to learn by trying something small enough to adjust. Guideposts can help teams notice when an assumption fails or a project needs a different course.
Small experiments reduce the cost of being wrong and make uncertainty observable. That logic appears in design prototyping and scientific inquiry: a crude test can answer a consequential question faster than a polished proposal. The approach also has a psychological effect, since visible progress counters the helplessness that large social problems can provoke. Still, not every important outcome can be tested through a short pilot. Slow-moving effects, rare harms, and system-wide consequences may require longer observation. A good experiment therefore specifies what it can reveal, what it cannot, and what evidence would justify scaling or stopping.
Turn shared intent into small, named promises with deadlines
No spectators in the plan. Shared leadership means responsibility moves among participants rather than belonging only to a designated boss. A short action plan translates a group's agreement into named tasks. For each task, specify who will do what, what they will produce, and by when. The authors recommend keeping plans close to a 30-day horizon because conditions can change and distant schedules often create false certainty.
Small promises build trust. Micro-commitments are modest, explicit actions that make it easier for people to follow through and see one another do the same. In a Pittsburgh university-community project, participants took on separate tasks to assess possible funding, gather stakeholder views, and identify potential spaces. The proposed center did not proceed as intended, but the work helped reveal a viable partnership between the university pharmacy school and county health department. Action created a useful connection even when the original plan changed.
A written commitment is a behavioral bridge between intention and execution. It makes responsibility visible, reduces ambiguity, and gives a group a basis for repairing missed expectations without relying on vague accusations. The modest scale is also psychologically credible: people are more likely to promise what they can realistically deliver. Yet accountability should not become a surveillance ritual. Workloads, authority, and access to resources differ, so identical commitments may not be fair. Strong shared leadership makes promises voluntary and specific, while allowing participants to renegotiate when circumstances change rather than treating every deviation as a character flaw.
Use regular reviews to build learning, trust, and momentum
Review and revise together. A learning loop is a recurring process for checking progress, interpreting results, and adjusting action. The authors call a common meeting rhythm 30/30: look back at the previous month, decide what was learned, and agree on the next set of actions. The interval is flexible. A faster-moving environment may call for weekly reviews, while a slower one may need less frequent check-ins. The essential habit is to schedule the next meeting before participants leave.
Question the plan itself. The book distinguishes routine correction from double-loop learning. A team should not only ask whether it is carrying out its plan, but also whether the plan's assumptions and goals still make sense. A group can also reinforce its work by nudging members to complete tasks, connecting new people and networks, and promoting visible progress. In a retirement savings example, changing the default to automatic enrollment raised participation above 90 percent, showing how environments can make a desired action easier.
Regular reviews create organizational memory. Without them, each meeting can become a fresh start, and teams repeat decisions without learning why earlier choices succeeded or failed. The deeper question about underlying assumptions is especially powerful because organizations often optimize procedures that no longer serve their purpose. Nudges can help sustain action by reducing friction, as automatic enrollment demonstrates. Their ethical use depends on transparency and a meaningful ability to opt out. In collaborative settings, reminders should support commitments participants chose, not quietly manipulate them toward priorities set by someone else.
Distribute leadership across people with different ways of seeing
No one holds every skill. The book treats leadership as a capacity shared across a group. One participant may be good at framing questions, another at spotting hidden resources, and another at keeping commitments on track. This distribution matters because complex environments contain more variables than a single person's knowledge can cover. The Law of Requisite Variety expresses the idea that a system needs enough variety in its responses to handle the variety it faces.
Use a repeating cycle. Strategic Doing organizes collaboration around four moves: surface opportunities from available assets, select and clarify a desired outcome, agree on a small starting project, then reconvene to learn and set the next actions. The sequence repeats as new information and participants enter. In a 50-university initiative, more productive teams reported using about eight of the ten skills on average, compared with about two among less productive teams. The authors note that this association does not establish cause.
The framework's most consequential implication is that leadership is not merely delegated downward; it is distributed according to the work at hand. This fits research on cognitive diversity, where varied problem-solving approaches can improve performance on complex tasks. Demographic diversity may bring valuable perspectives, but visible difference alone does not guarantee different ways of reasoning or equal influence. Variety also creates coordination costs. Shared leadership therefore depends on clear conversational rules, roles, and follow-through, not just assembling a diverse group. The university comparison is suggestive rather than conclusive, since stronger teams may use more skills because they are already better organized.
Analysis
Strategic Doing reframes strategy as a practiced capacity for coordinating action among people who cannot simply be ordered to comply. That is its central contribution. Instead of treating analysis as the precondition for action, it treats modest action as a way to generate knowledge, relationships, and strategic options. The method's sequence is memorable because it connects social conditions, imagination, resources, selection, experimentation, and accountability. Its recurring cadence makes strategy less like a prediction about a fixed future and more like disciplined adaptation.
The approach is especially persuasive for problems that cross organizational boundaries: regional development, public health, innovation, and university-community partnerships. In such settings, authority is fragmented, knowledge is distributed, and no actor possesses all the resources required. The emphasis on explicit commitments is more than project management. It converts trust from a warm sentiment into observable conduct: people do what they said they would do, and the group responds when conditions change.
Several limits deserve attention. Asset-based thinking can help a group begin, but it cannot substitute for funding, public authority, or redress of entrenched inequality. Asking people to creatively recombine what they have may unintentionally normalize chronic scarcity. Appreciative questions can energize participation, but a focus on possibility should not suppress difficult evidence about harm or structural causes. Likewise, small pilots are useful only when their scope matches the claim being tested; local success may not scale to a larger system.
The framework is therefore strongest when paired with honest diagnosis, transparent power-sharing, and evaluation appropriate to the stakes. Its promise is not that every complex challenge can be solved through better meetings. It is that groups can become more capable of acting together, learning in public, and revising their direction before delay hardens into failure. The book's best practical insight is that collaboration is not an attitude to announce. It is a set of behaviors to design, practice, and keep renewing.
Review Summary
Strategic Doing receives mixed reviews, with an overall rating of 3.92 out of 5. Many readers find it practical and insightful for collaborative project management and agile leadership. The book's ten skills for agile leadership are praised for their applicability in various settings. Some reviewers appreciate its focus on leveraging assets and creating measurable outcomes. However, critics find the content underwhelming, lacking novelty, or poorly organized. Several readers note that while the concepts are familiar, the book provides a useful framework for implementation, particularly in community and organizational development contexts.
People Also Read
Glossary
Strategic Doing
Iterative network strategyA collaborative approach to strategy designed for open networks in which participants are not all part of one chain of command. People identify available resources, create and prioritize opportunities, define a shared outcome, begin a manageable project, and meet regularly to learn and adjust. The approach treats strategy as an ongoing practice rather than a fixed long-range plan.
Big Easy
High-impact, feasible opportunityA method for choosing a useful first opportunity by comparing options on two dimensions: potential impact and ease of implementation. A simple matrix helps a group make its judgments visible and discussable. The selected option should matter enough to engage people while being practical enough to start, so early action can build confidence and trust.
30/30
Recurring review meetingA regular team meeting that looks back at a recent period, often 30 days, to review what happened and what was learned, then plans the next period of work. The timing can be shortened or lengthened to fit the pace of change. Its purpose is to make review, adjustment, and renewed commitments a habit.
Appreciative Inquiry
Strength-focused inquiryAn approach to group inquiry that explores strengths, successful experiences, and desired possibilities rather than organizing the entire discussion around deficits. In this book, appreciative questions help participants imagine what they want more of and identify resources that could move them toward it. The method does not require ignoring problems; it redirects discussion toward constructive action.
micro-commitments
Small, explicit promisesModest actions that participants voluntarily promise to complete as part of a shared effort. A useful commitment identifies an owner, a specific task, a deliverable, and a deadline. Keeping these small promises gives a group observable evidence that members can rely on one another, while making participation manageable alongside existing work and responsibilities.
learning loop
Review, learn, adjustA recurring process in which a team checks results, discusses what those results reveal, and changes its next actions. Unlike a one-time evaluation, a learning loop feeds evidence back into ongoing work. The deeper version also examines whether the original assumptions or goals remain appropriate, rather than merely correcting execution.
Law of Requisite Variety
Match response to complexityA principle associated with cybernetician W. Ross Ashby: a system needs enough variety in its responses to deal with the variety in its environment. Applied to collaboration, the idea suggests that complex challenges are unlikely to be handled well by one person's limited skills and perspective. A group needs varied capabilities and ways of interpreting problems.
prospection
Imagining a possible futureThe act of mentally representing and exploring a future outcome. The book uses prospection to help groups move beyond vague aspirations by describing what success would look like, how it would feel, and whose lives would change. Such concrete future images can help participants understand whether they share an outcome and what it might mean in practice.
S-Curve
Growth and decline patternA model of change in which an innovation, organization, or other system begins slowly, grows rapidly, reaches a plateau, and may then decline. The book uses the curve to show why success is temporary and why organizations should prepare for emerging opportunities before current strengths lose momentum. Moving to a new curve involves uncertainty and experimentation.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.