- Page 1:
Strategy Strategy Survival Survival
- Page 4 and 5:
Strategy Survival Guide Version 2.1
- Page 6 and 7:
Building an Evidence Base 113 Data
- Page 8 and 9:
A Framework for Strategic Direction
- Page 10 and 11:
These four components need to be co
- Page 12 and 13:
Strategy Survival Guide Version 2.1
- Page 14 and 15:
Strategy Survival Guide Version 2.1
- Page 16 and 17:
Strategy Survival Guide Version 2.1
- Page 18 and 19:
Strategy Survival Guide Version 2.1
- Page 20 and 21:
Strategy Survival Guide Version 2.1
- Page 22 and 23:
Strategy Survival Guide Version 2.1
- Page 24 and 25:
Strategy Survival Guide Version 2.1
- Page 26 and 27:
Strategy Survival Guide Version 2.1
- Page 28 and 29:
Strategy Survival Guide Version 2.1
- Page 30 and 31:
Strategy Survival Guide Version 2.1
- Page 32 and 33:
Strategy Survival Guide Version 2.1
- Page 34 and 35:
Strategy Survival Guide Version 2.1
- Page 36 and 37:
Strategy Survival Guide Version 2.1
- Page 38 and 39:
Strategy Survival Guide Version 2.1
- Page 40 and 41:
Strategy Survival Guide Version 2.1
- Page 42 and 43:
Strategy Survival Guide Version 2.1
- Page 44 and 45:
Strategy Survival Guide Version 2.1
- Page 46 and 47:
Strategy Survival Guide Version 2.1
- Page 48 and 49:
Strategy Survival Guide Version 2.1
- Page 50 and 51:
Recruiting a team In Practice: SU G
- Page 52 and 53:
• Commitment to a common purpose
- Page 54 and 55:
Away-days A project away-day is ano
- Page 56 and 57:
WHY ...are you telling me this? SO
- Page 58 and 59:
Strategy Survival Guide Version 2.1
- Page 60 and 61:
Try to put into practice the princi
- Page 62 and 63:
Encouraging creativity In Practice:
- Page 64 and 65:
There are clear differences between
- Page 66 and 67:
Strategy Survival Guide Version 2.1
- Page 68 and 69:
Strategy Survival Guide Version 2.1
- Page 70 and 71:
Strategy Survival Guide Version 2.1
- Page 72 and 73:
Strategy Survival Guide Version 2.1
- Page 74 and 75:
Strategy Survival Guide Version 2.1
- Page 76 and 77: Strategy Survival Guide Version 2.1
- Page 78 and 79: Strategy Survival Guide Version 2.1
- Page 80 and 81: Identifying key stakeholders and th
- Page 82 and 83: Engaging with stakeholders Having i
- Page 84 and 85: Strategy Survival Guide Version 2.1
- Page 86 and 87: • What channels do we know don’
- Page 88 and 89: Strategy Survival Guide Version 2.1
- Page 90 and 91: Preparing the Story Once you have a
- Page 92 and 93: Strategy Survival Guide Version 2.1
- Page 94 and 95: development process include brainst
- Page 96 and 97: Strategy Survival Guide Version 2.1
- Page 98 and 99: Strategy Survival Guide Version 2.1
- Page 100 and 101: Reinforcing Loops A + Balancing Loo
- Page 102 and 103: Structuring the thinking - Systems
- Page 104 and 105: Opportunities • Where are the goo
- Page 106 and 107: Strategy Survival Guide Version 2.1
- Page 108 and 109: Structuring the thinking - PESTLE I
- Page 110 and 111: Revolution This is creativity at it
- Page 112 and 113: For example, Sub-problem: My collea
- Page 114 and 115: Structuring the thinking - Creativi
- Page 116 and 117: Strategy Survival Guide Version 2.1
- Page 118 and 119: in The Magenta Book) are rigorous m
- Page 120 and 121: Strategy Survival Guide Version 2.1
- Page 122 and 123: • Avoid asking the same question
- Page 124 and 125: Expectations can be shaped by a num
- Page 128 and 129: Strategy Survival Guide Version 2.1
- Page 130 and 131: Collecting data - Interviews & focu
- Page 132 and 133: Step One: Define the problem explic
- Page 134 and 135: • Are the units correct? Step Sev
- Page 136 and 137: Analysing data - Modelling In Pract
- Page 138 and 139: Strategy Survival Guide Version 2.1
- Page 140 and 141: The Five Forces Framework can be us
- Page 142 and 143: References Structure, Conduct, Perf
- Page 144 and 145: Strategy Survival Guide Version 2.1
- Page 146 and 147: Symbols • What language and jargo
- Page 148 and 149: Strategy Survival Guide Version 2.1
- Page 150 and 151: • Put a contact name, telephone n
- Page 152 and 153: Learning from others - Internationa
- Page 154 and 155: 4. Functional Benchmarking or Gener
- Page 156 and 157: Strategy Survival Guide Version 2.1
- Page 158 and 159: Strengths • Quantitative forecast
- Page 160 and 161: Strategy Survival Guide Version 2.1
- Page 162 and 163: 3. Bring drivers together into a vi
- Page 164 and 165: Scenario development In Practice 1:
- Page 166 and 167: Scenarios used in the Strategy Unit
- Page 168 and 169: groups at random. In other words, t
- Page 170 and 171: Strategy Survival Guide Version 2.1
- Page 172 and 173: events. There are a number of diffe
- Page 174 and 175: Multi-criteria analysis In Practice
- Page 176 and 177:
Strategy Survival Guide Version 2.1
- Page 178 and 179:
Cost-benefit & cost-effectiveness a
- Page 180 and 181:
Strategy Survival Guide Version 2.1
- Page 182 and 183:
For further material, see the Ratio
- Page 184 and 185:
Strategy Survival Guide Version 2.1
- Page 186 and 187:
Compelling vision for action - the
- Page 188 and 189:
Strategy Survival Guide Version 2.1
- Page 190 and 191:
Strategy Survival Guide Version 2.1
- Page 192 and 193:
Designing an implementation plan In
- Page 194 and 195:
Creating Public Value http://www.nu
- Page 196 and 197:
National Statistics http://www.stat
- Page 198 and 199:
Strategy Survival Guide Version 2.1
- Page 200 and 201:
Strategy Survival Guide Version 2.1
- Page 202 and 203:
Strategy Survival Guide Version 2.1
- Page 204 and 205:
Driver trees 97 Econometric modelli
- Page 206 and 207:
management 17, 20, 27, 34, 45 outpu
- Page 208:
Strategy Unit, Admiralty Arch, The