15 March 2026

Strategic Thinking - Weekly Update

Have been training on how to think.. here is overall progress....

 

Elite Think Tank Mastery Program

Systems Thinking Cognitive Training Report

Author: Lakshmi Narayanan Narasimhan
Program: Elite Think Tank Mastery
Training Focus: Systems Thinking • Strategic Reasoning • Structural Diagnosis


Program Overview

The Elite Think Tank Mastery Program is a long-term cognitive training initiative focused on developing deep expertise in systems thinking and strategic diagnosis.

The program trains the ability to understand complex systems through causal mechanisms and system archetypes.

Core analytical framework used throughout the training:

Events
  ↓
Causal Mechanisms
  ↓
System Archetypes
  ↓
System Behavior
  ↓
Strategic Intervention

The objective is to develop the ability to identify structural drivers behind system behavior, rather than reacting to isolated events.


Current Training Status

MetricValue
Total Drills Completed1755
Foundation Target2500
Completion≈71%
Average Accuracy≈98%

Progress Visualization

0        500       1000       1500       1755        2500
|--------|---------|----------|----------|-----------|
Start    Phase 1   Phase 2    Phase 3    Current     Foundation Complete

Remaining drills:

2500 - 1755 = 745 drills

Today's Training Summary

Drill Types Practiced

  • Archetype Recognition

  • Reverse Diagnosis

  • System Collapse Analysis

Drills Completed

20 drills

Accuracy

≈98%

The training session maintained a high accuracy level across multiple system diagnosis scenarios.


Drill Categories

Archetype Recognition

Identifying the system archetype based on a causal mechanism chain.

Example:

Growth
 → Coordination Complexity
 → Decision Bottleneck
 → Execution Slowdown

Archetype:

Limits to Growth

Reverse Diagnosis

Starting with observable system behavior and identifying the underlying structural causes.

Example:

Outcome
Industry margins declining

Diagnosis:

Competition
 → Price Reduction
 → Competitive Response
 → Price War

Archetype:

Escalation

System Collapse Analysis

Analyzing complex scenarios where multiple mechanisms interact.

Example:

Failure
 → Risk Aversion
 → Control Expansion
 → Decision Bottleneck
 → Innovation Decline

Archetypes:

  • Control Expansion

  • Limits to Growth


Archetype Coverage

The following system archetypes have been practiced extensively:

ArchetypeDescription
Limits to GrowthGrowth constrained by emerging bottlenecks
Success to the SuccessfulReinforcing advantage loops
Growth & UnderinvestmentCapacity expansion lagging demand
EscalationCompetitive response loops
Shifting the BurdenShort-term fixes replacing structural solutions
Control ExpansionBureaucratic response to risk
Tragedy of the CommonsShared resource overuse
Success Lock-inPast success creating structural inertia
Feature CreepContinuous feature additions causing complexity

These archetypes represent recurring structural patterns across organizations, markets, and systems.


Example System Diagnoses

Organizational Scaling Problem

Growth
 → Team Expansion
 → Coordination Complexity
 → Decision Bottleneck
 → Slower Product Releases

Archetype:

Limits to Growth

Platform Ecosystem Expansion

Users
 → Creators
 → Content
 → More Users

Archetype:

Success to the Successful

Infrastructure Congestion

Population Growth
 → Infrastructure Investment Lag
 → Private Vehicle Increase
 → Traffic Congestion

Archetype:

Growth & Underinvestment

Cognitive Development Timeline

Phase 1 (0–500)
Mechanism Recognition

Phase 2 (500–1000)
Basic Archetype Recognition

Phase 3 (1000–1500)
Advanced Archetype Diagnosis

Phase 4 (1500–1800)
Multi-Archetype System Reasoning

Phase 5 (1800–2200)
Strategic Leverage Thinking

Phase 6 (2200–2500)
Advanced System Diagnosis

Current stage:

Phase 4 – Multi-Archetype System Reasoning

Cognitive Capabilities Emerging

At approximately 1750 drills, the following abilities are becoming consistent:

• Long causal chains (6–10 mechanisms)
• Identification of primary and secondary archetypes
• Diagnosis of system collapse patterns
• Structural reasoning across domains

This indicates the transition from pattern recognition to system diagnosis.


Next Milestone

Next checkpoint:

1800 drills

Remaining:

≈45 drills

This milestone introduces the next training capability:

Leverage-Point Identification

Example:

Growth
 → Coordination Complexity
 → Decision Bottleneck

Strategic intervention:

Decentralize decision authority

Long-Term Training Objective

The ultimate goal of this training program is to develop the capability to diagnose complex systems across domains including:

• organizations
• technology platforms
• economic systems
• infrastructure networks
• innovation ecosystems

The conceptual framework developed through this program is referred to as:

Causal Systems Diagnostics

Future Training Areas

Upcoming areas of exploration include:

  • Strategic leverage-point analysis

  • Multi-archetype system interaction

  • System collapse patterns

  • System resilience design

  • Strategic ecosystem dynamics

These will form part of a larger systems thinking knowledge base.


Closing Note

Complex systems rarely fail due to isolated events.

They evolve due to structural mechanisms embedded within the system.

By systematically studying causal mechanisms and archetypes, it becomes possible to diagnose and anticipate system behavior with greater clarity.

This training program represents an ongoing effort to develop that capability.

 


06 December 2023

14 August 2023

Back Again To Blog

 It has been a while since I wrote anything.

Almost like three years since I wrote something useful, meaningful. (this is debatable, you could argue that I never wrote anything useful which I will flight to prove you wrong, but I know you will eventually win ;-))

I can blame "the busyness" at work, health, personal life (everyone has everything, but they still do it)

The processors are never idle. When they do not have any instructions to run, they kill the time by doing "No operations" - an idle task.

How one can kill time - by idle, thinking about things that are non-existent, neither useful, imagination of future (leading to anxiety) and retrospection of the past (leading to guilt, anger) without any concrete outcomes. Killing time is by hobby. Oh no, it started as a hobby eventually I have become a subject-matter-expert

The truth is - I have not been reading as much as I could (which equals to reading nothing).

For me, the confidence level takes a hit, when I stop learning. Regaining confidence takes a time.

 What i m going to do - read stuff on the things I have been doing recently and probably learn doing things at scale.


06 September 2021

Building a Tribe - Sweet Spot

Building a "Tribe" is much more important than anything else. 100% of the time, "The Tribe" gets done everything, always delivers more than what is stated. It takes a while for the tribe to get there, but once the tribe reaches there, the tribe fires all cylinders - it is called the sweet spot.

Random signs of sweet spot:
  1. Individuals support the tribe without being asked
  2. Individuals care for the tribe than they do for themselves
  3. Individuals believe that they can do anything (comes the confidence they have on the tribe)
  4. Individuals believe that they can influence the outcomes
  5. Communicate well
  6. Organize themselves better
  7. Happy to downplay, happy to level-up
  8. Blunt and cut-throat in saying what they feel (never gets ashamed of saying something)
  9. Feel reduced without their tribe
  10. Share (credits, knowledge)
  11. They do not need managers, they manage themselves
  12. Try to create a "Zero Entropy" system
  13. Keep reinventing
  14. Grow themselves and the tribe
  15. Gossip less

18 June 2019

Hashmaps - Python

It has been a while that I wrote some code. Been learning Python using Udemy for some time. Python is truly expressive and batteries included language. I read about Hashmaps and thought I should give it a try. Within a very short duration (say 1 hour), I was kind of able to complete full hashmap implementation along with basic tests using PyTest. My coding screenshots. You can also check out my GitHub (that has Jupyter notebook file)











05 June 2019

Visualization in Python - Case Study: Urban Accidents in India

I was reading a news item related to accidents and wanted to explore more. With a bit of search, I landed in Govt of India Data website. The website had so much data and visualization in different industries/areas. With another double down, I managed to download the data for Urban accidents in all Indian states.

With a couple of hours of staring at the data and coding, managed to pull out the following charts. The data had absolute numbers for each state and I had come up with a ranking on the following KPIs (had to download population data from Wikipedia according to 2011 census report)

  1. Number of urban accidents
  2. Percentage of accidents with a weighted urban population
Feedback loop: Data -> Information -> Insights -> Business Transformation

Tools Used:
  1. Python (no Numpy or anything else)
  2. Matplotlib for visualization
  3. Jupyter to cook Python code quickly
Source code and visualization can be found in my github repo

Questions:
  1. Why GA has more accidents than TN? (why??)
  2. Why HP has more accidents than PY? (terrain?)
  3. What can be done to minimize accidents?
Visit www.geekshub.in to know more and learn more on Python/Go/Cloud/Cloud Native/Javascript

15 April 2019

GeeksHub

As some of you know that I used to do the mentoring of students to improve their employability at a personal capacity. I thought I should give a formal structure to it as I continue to create impact. We are seeing career transformation and the time is just right.

I am merging my contributions in mentoring through GeeksHub, where I will be serving as an advisor. GeeksHub is an upskilling company primarily targeting entry and mid-level software engineer to improve their hard skills (coding, technology and related). You can find more about them here

I will continue to use this blog for technical/technology discussions and others related to technology. I will refrain posting general stuff related to life (but you never know)

More on GeeksHub in next post :-)

14 February 2019

Attitude to Learn

A new thing resets competency and level sets the competition. People sitting near the fence waiting for "right time" to jump in and take a dip often end up being a latecomer and take up what is leftover.

There is a clear advantage of being a lifelong student. Learning pays linearly, the attitude of constant learning pays exponentially.

Agree?hashtag

16 October 2018

Master, Expert and Machine

To build something new, you need a master. To improvise something that is built, you need an expert. To run something that is already built/improved, you need a machine

The points are:
  1. To build a software you need a master, to sustain it you need an expert and to operate it, you need a machine.
  2. To build quality you need a master, to improve it you need an expert and to just regress the past, you need a machine
These are phases and need not be necessary done by different people. The skills required diminishes as we traverse the phases (so are complexity)

Build -> Sustain -> Run requires Master -> Expert -> Machine

08 October 2018

Upskilling is the mantra

The future needs a functional guy – someone who sees the customer and her pains.

DevOps is more than set of tools, a framework to add business value and reduce customer pain. Someone who can respond to pain like a doctor in emergency not just taking a note of the situation.

Cloud developer is not just a developer. The fast paced world needs him to be everything. He needs to be “Agile” – groom his stories, make an initiative to understand the business requirements, develop them into a piece of functionality, test them, automate them so that it cries when something is broken, document everything that needs to be and act on the feedback. Be a positive feedback machine.

I don’t want to be a dev guy and I don’t want to be a test/automate. There is no space for someone who wants to sit in dev or test and just do what he is skilled at. The newer world needs someone who gets excited to jump on the unknown and gets the hands dirty and quickly build expertise (just what is needed).

Overall, an outcome based, customer focused tribe capable of scaling horizontally and vertically over a period of time.

Upskill is more of mindset than a skillset

So, Upskilling is the mantra

10 January 2018

Get, Set, GOLANG

[Reading Time: 3 to 5 minutes]

[Edited] Reposting this as i have decided to change the book.

Looks like programming languages are sweeping the internet today. Ever since the programming languages were introduced, the pace of new languages was rising gradually. Today, we are seeing a higher pace of several new and promising languages. Python and Go seem to take up cloud software development quite strongly. Python has been around for a lot of time. Go seems to pick up - offering ease of development comparable to languages like Python and giving a speed of execution of that of C/C++. From now and for next few months, I have to ride two horses - learning both Python and Go. I have to admit that I cannot put off my temptation (which I kept off for last three months).

Go in Action by William Kennedy
Go in Action by William Kennedy
and Others
Similar to Python, my goal is to become fluent in Go. I am not sure of the timeline but I do see a compelling need to be good in Go in near future. I would like to take up this self-learning of Go by reading books and trying out exercises in GitHub. Having decided to learn Go, I was searching the internet for where to start. There are several good books out there. Go in Action is one among them which was highly recommended in a couple of forums. Being decent sized book (not too small or not too big) and based on my first impression after reading the table of contents, I feel that it would provide a good start in my journey.

It consists of 9 chapters (270 pages). The chapters are said to be designed in such a way that an intermediate programmer can get best out of it (the audience the folks with some programming experience but new to Go, so no boring stuff). This is a quite a promise to keep up. I am excited to ride two horses.

Let us see how it goes. I am excited to learn Go and share my reading journal with you on Go :-)

There is another language that is creating so much noise - Rust. Check it out. If you are a C guy, you have to watch out Rust (hoping that I will not jump the gun in learning Rust)

Note 1: You will see "Reading Time" in all my posts. I want to alert you how much time you are likely to invest reading my posts so that you can decide when and whether to read the post.
Note 2: My goal is to keep it short and give you links in every page to read posts relevant each post

[Update after reading first chapter and reading the second chapter after half way through]
Looks to me that Go In Action has taken the learning in a different perspective and I am certainly feeling little tired to get past each sections. Somehow, I feel this should not be my first book on Go and I am going to switch to another book - which probably offers step by step in small increments.