Kalle reflects on The C-list
The C-step mirrors the brainstorming phase of strategic frameworks. The flow of ideas in strategic thinking begins with A, the goal or vision. B describes your current situation in relation to that goal. In the C-step, you systematically identify and list possible measures—“stepping stones”—that could bridge the gap between B and A.
If the C-list is too thin or superficial, you run into the classic “poor data in, poor results out” problem when you reach D, where actions are prioritized. With too few—or insufficiently diverse—options on the C-list, meaningful prioritization in the D-step becomes difficult or even impossible.
- “We improved our bottom line initially, but results have now plateaued.”
- “There are too many uncertainties, for example due to changing political conditions.”
- “We are unsure how to manage trade-offs in this particular case.”
- More people are involved, including additional internal departments, value-chain partners, and broader stakeholder groups.
- These groups collaboratively generate a wider range of possible solutions on C-lists.
- More attractive product and service designs that offset higher costs associated with sustainability innovations.
- Joint procurement across stakeholders to reduce costs through increased purchasing volumes.
- Identification of new markets willing to pay higher production costs.
- Reducing vulnerability of a certain pathway, by finding another.
- Engagement with policymakers to support regulatory frameworks, such as green taxes, that favor innovation. Which is often possible at municipal levels where some taxes can be determined directly.
- For comparison, you may also consider how the expansion of C-lists is useful in other complex games within complex systems. For instance, chess players consider many options before making a move at the final D step. Similarly, football teams explore innovative ways to improve performance ahead of the next match. In both cases, the lists of ideas are naturally processed within the same ABCD logic inherent to the more specific frameworks of the respective games.
Fact box – a Shared Code behind all Reflections, Podcasts, and other developments at www.stepwise.global
To keep each Reflection self-contained, we include only what is essential in the main text. This helps avoid unnecessary length, while reducing the risk of flawed or oversimplified interpretations of key elements of the Operative System—such as the Funnel, Boundary Conditions, and the ABCD process—that are common in other sources.
For example, some sources incorrectly suggest that “A” stands for “Awareness.” It does not. “A” is simply the first letter of the alphabet, reminding us that strategic thinking begins with the goal in mind—through backcasting.
In this logic:
A = the desired future state (goal or vision)
B = your current situation in relation to that goal
C = a brainstormed list of possible measures to bridge the gap
D = the prioritization of those measures into a smart, stepwise plan
You can explore these concepts in more detail through any of the links below:
1. Scientific foundation
Access the peer-reviewed research directly:
doi.org/10.1002/sd.3357
________________________________________
2. Practical overview
See the Operative System at https://fssd.global/framework-and-method/
________________________________________
3. Explore and apply
Visit: https://www.stepwise.global and explore:
• How the Operative System ‘ABCD-in-Funnel’ works in practice
• Kalle’s Reflections
• Podcasts and real-world applications
…to train the Operative System without losing the code’s systemic,
systematic, or strategic perspective.
________________________________________
4. Courses and learning opportunities, sign up for course options via our
homepage.

