The Problem That Kept Coming Back
Vikram ran infrastructure for a logistics company in Chennai. He was methodical, respected, and known for fixing things. Over eighteen months, he redesigned the same handoff process three times.
Each iteration was more refined than the last. Each one failed at a different point for what looked like a different reason. By the third cycle, his team assumed the process itself was broken beyond repair. Vikram had started to agree with them.
The standard advice in this situation is to go deeper into root cause analysis. Use the five-whys. Map the system more completely.
Add more eyes to the review. Vikram had done all of this. He had a whiteboard full of fishbone diagrams and a team that had stopped believing the diagrams would help.
The frameworks were not the problem. The frameworks were fine. What nobody examined was the state Vikram entered every time the problem surfaced.
When the process failed, Vikram went into high-performance task completion mode. He was focused, fast, and completely locked onto the visible symptom. In that state, he fixed exactly what he could see.
What he could not see, because of the state he was in rather than any gap in his knowledge, was the upstream configuration that kept regenerating the symptom. He was solving at the level the state allowed him to see. That level was always one layer too shallow.
State Configuration and Why It Changes Everything
Antano makes a distinction that few professionals have heard before they sit with him. He separates the world of input from the world of response, and places state in between. What you receive from the world, and what you decide and do about it, are not directly connected.
They are filtered through whatever state you happen to be running at the moment of contact. State one produces one set of conclusions. State two produces a different set.
State five produces something different again. The inputs are the same. The outputs are not.
This is why the conventional approach to how to improve problem solving skills falls short. Techniques address what happens after the state has already made its selection. You are learning how to structure the information that your current state has already filtered.
If the state is selecting for speed, you get fast solutions at the wrong level. If the state is selecting for political safety, you get solutions designed not to fail visibly rather than solutions designed to work. The technique sits downstream of the state.
Changing the technique while leaving the state unchanged produces marginal improvement at best.
What Antano and Harini address is state configuration directly. This includes collapse anchors, which give a person genuine choice in a specific context where they previously had a locked response. It includes understanding what triggers a state, whether that trigger is external (something in the environment fires the pattern) or internal (intent fires the pattern).
And it includes installing the capacity for the right state to activate based on what the situation actually requires, not based on what the situation resembles from past experience. When state choice is operational, the problem solving that follows is fundamentally different in quality. Not because new techniques have been added, but because the state receiving the problem is selected for what this particular situation needs.
What Solving at the Root Actually Looks Like
Vikram's situation did not change because he learned a new framework. It changed because Antano worked with the state he entered when the process failed. In that reactive mode, Vikram was essentially a machine.
Input the broken handoff, output the patch. The patch was always technically correct. It never addressed the configuration that produced the handoff failure in the first place, because that configuration was only visible from a different state. One that Vikram did not have access to in the moment the problem appeared.
After EIT work, the same triggering context produced a different internal response. The loud alarm of a failed process, which had previously pushed Vikram into sprint mode, began to cue a different state. One with broader scope, slower selection, and access to the upstream configuration.
In that state, Vikram saw something he had seen the data for many times without registering: the handoff failure was a consequence of a resourcing decision made four weeks earlier. It was never a handoff problem. It was a planning horizon problem wearing handoff clothes. Once he saw it from the right state, the fix was straightforward and it held.
This is what root-level problem solving produces. Not a more sophisticated version of the same solution pattern, but access to the actual problem. The clients who come to Antano and Harini and say they want to improve their problem solving skills are usually not asking the wrong question.
They are asking it at the wrong level. The skills they need are already largely present. What is missing is state choice: the ability to select the configuration that matches the problem at hand, rather than running the configuration that the problem triggers by default.
That is a capability. It is installable. And once it is in place, the same person who was solving symptoms begins solving causes.
Watch Antano work with this pattern live
The video series shows the session dynamic in full, including exactly where the intervention lands and what changes in the person in the room.
Watch: Solve Problems at the Root