Most of my career has been under the title of “strategist”. I’ve had to steer many client organizations away from jumping the gun on tactical thinking by convincing them strategy is qualitatively different and important.<p>My experience is that strategic planning is about the “what”. What should we even be doing? As important, what should we NOT be doing? Given our limited time and resources, what is an efficient approach to winning the game we are playing (or do we even need to identify the game and define winning first)? Question everything. Challenge assumptions.<p>Mostly ask “what” and “why”, sometimes “who” and “where”.<p>Tactical planning is about “how”. How can we effectively implement the strategy? Without challenging the assumptions that got us here, and assuming we’re already stuck with the game and the rules our strategy selected, how do we win? No more resources are coming. Too late to ask hard questions (except to use as input for next time we do strategy). Execute to maximize effectiveness; worry about efficiency only secondarily.<p>Mostly ask “how”, sometimes ask “where” and “who”.
This explanation doesn't separate the terms "tactic" and "strategy". In fact it mixes them together, he even says a tactic is basically a substrategy.<p>If you're using recursion, that should be clear. Just call everything a strategy, or everything a tactic.<p>Fact is this distinction between these terms has never been real in any sense. People vaguely use strategy to mean "big picture" and tactic to mean "particular action", but if you decompose it you'll see more little strategies inside.<p>This is true in many game-like situations.
All these words to say a few simple things...<p>Tactics are smaller-scale than strategy. Tactics is the implementation details and strategy is the big picture. Tactics are the movements of chess pieces and strategy is the intent of those movements.
From Wiki: On 30 January 1698, Kidd raised French colours and took his greatest prize, the 400-ton Quedagh Merchant,[18][19] an Indian ship hired by Armenian merchants that was loaded with satins, muslins, gold, silver, an incredible variety of East Indian merchandise, as well as extremely valuable silks. The captain of Quedagh Merchant was an Englishman named Wright, who had purchased passes from the French East India Company promising him the protection of the French Crown. After realising the captain of the taken vessel was an Englishman, Kidd tried to persuade his crew to return the ship to its owners,[citation needed] but they refused, claiming that their prey was perfectly legal, as Kidd was commissioned to take French ships, and that an Armenian ship counted as French, if it had French passes. In an attempt to maintain his tenuous control over his crew, Kidd relented and kept the prize. When this news reached England, it confirmed Kidd's reputation as a pirate, and various naval commanders were ordered to "pursue and seize the said Kidd and his accomplices" for the "notorious piracies" they had committed.[20]<p>Kidd kept the French sea passes of the Quedagh Merchant, as well as the vessel itself. While the passes were at best a dubious defence of his capture, British admiralty and vice-admiralty courts (especially in North America) heretofore had often winked at privateers' excesses into piracy, and Kidd may have been hoping that the passes would provide the legal fig leaf that would allow him to keep Quedagh Merchant and her cargo. Renaming the seized merchantman Adventure Prize, he set sail for Madagascar.
This is an unfortunately terrible article.<p>It's overly long, convoluted, and the central pirate anecdote works only to obscure the core principles.<p>There is an attempt here to 'ape' the style of similar, more enlightening pieces, but they've really gotten lost along the way.
I've learned the difference between strategy and tactics through agile development.<p>During our pre-planning and sprint planning sessions, our PO usually lays out a plan of our priorities (strategy) occasionally he will suggest implementation plans (tactics) as one is want to do for an engineer turned product owner, but I always try to take a step back and ask him "what sort of system do you want".<p>It's been a few years since he was a day to day developer, he's not as well versed in the new modules and functionality (tactics) that are now built into the system, often times he'll go into tactical discussion but it'll be off base because the resources we'd use to execute those tactics have changed. By trying to understand his intent and strategy I've been able to deliver what he wants but have the freedom to implement it in my own way.
For me, the first of the two most interesting points in this account was largely missing: Why exactly did Lord Bellomont turn against Captain Kidd?<p>The 2nd most interesting point: From Captain Kidd's point of view, and looked at objectively, Captain Kidd was an innocent man! He was carrying out a legitimate privateer commission! He had documents supporting this, but the facts and those documents were suppressed by rich and powerful people. In a way, Captain Kidd was killed by fake news, and his reputation to this day is still affected.
Here are some rules of thumb that have helped me design strategies and tactics for my clients:<p>1) The already mentioned "what" and "how" distinction<p>2) Phrase the strategy as an already-completed state of being, that is false now but will be true when met<p>3) Each strategy can have only ONE supporting tactic (which can be a verby action statement)<p>4) Each tactic can have 2:n multiple sub-strategies.<p>5) A sub-strategy can support multiple tactics.<p>You end up with a DAG.<p>In engineering in particular, the biggest impediment is that technicians tend to describe tactics when trying to describe strategies. I'm often asking, "Yes, but what objective does that meet?" or some such in response. And sometimes their answer is circular - the objective that it meets is that it eliminates the absence of their favored solution. Some people honestly never understand past that point. You have to pick your battles.
From the information gathered in the article and from other comments to me the distinction seems: tactic is a granular method for a problem that does not depend on previous tactic. Strategy is the conjuction of methods, tactics or substrategies however high-level your top-most strategy is, that depend on the previous outcome.<p>Strategy is like markov chain where each state is a subpart of the problem, and each state transfer to other state a tactic with varying success probability. But since the exact definition is not mathematical it will always be a little ambiguous.
Threadjack: if this sort of thing interest you, and want to hear other opines about strategy, tactics and their use through history, plus some modern anecdotes: I've been listening to and enjoying <i>Strategy: A History</i> by Lawrence Freedman on my commutes to work the last few weeks.<p><a href="https://www.amazon.com/Strategy-History-Lawrence-Freedman/dp/1501227726" rel="nofollow">https://www.amazon.com/Strategy-History-Lawrence-Freedman/dp...</a>
I would have liked more discussion about how the available tactics shape the strategy. It seems there is generally some circularity that needs to be navigated when constructing a plan to meet a non-trivial goal.<p>It is also important to acknowledge the higher-level concept above strategy -- e.g the vision, mission, or end-goal. Alternatively, this higher level can be framed as a specific, tangible problem that needs to be solved.
Pretty cool pirate story ! But I prefer chess to comprehend strategy vs. tactics.<p>Tactics:<p><a href="https://chesstempo.com/tactical-motifs.html" rel="nofollow">https://chesstempo.com/tactical-motifs.html</a><p>Strategies:
<a href="https://chesstempo.com/positional-motifs.html" rel="nofollow">https://chesstempo.com/positional-motifs.html</a>
My old MBA boss would use them interchangeable, saying things like "tactics can be strategic" and "strategy can be tactical." In the dictionary it says Strategy is long term plans, and tactics are short term plans.<p>Strategy is where you want go / do / be and tactics are how you get there.
Ghengis Khan victories and successful conquest was due to the fact his faith in his Generals. He would give them the overall strategy, "flank the opposing army", and expect his Generals to figure out the tactics to achieve the overall goal of winning the battle.
I'm not sure there was much ambiguity in defining strategy versus tactics in the first place. This article's convoluted use of "end states" and "actions" was not very helpful in solving this non-issue.
Savielly Tartakower's take on the distinction:<p>"Tactics is knowing what to do, when there is something to do. Strategy is knowing what to do, when there is nothing to do."