We are all so busy and huffing and puffing with so much going on in our plates. With so much information coming in the digital technology world, it is imperative for us to see where we are going and what our goal is without which we will miss the most crucial information which is already in our hands. Catching up is inevitable in a fast-moving world but wasting time on analyzing and interpreting with no results is not acceptable. That is why structural thinking is necessary for our daily day=to-day life. I was not familiar with this term until I was 34 years old. When I was working for a premier R & D organization, I heard of this term a lot in the meetings when the young engineers were talking about structural thinking to design and develop a MIMD high-performance parallel computer and a system software needed to run it. But it came in and went out as I was not involved in those activities and my role was managing the finances of the premier R & D organization. We all know we feel the heat only when we are thrown into the fire. I moved to the US and was handling structuring the proposals and associated financial models for multi-year multi-million-dollar proposals going out to Fortune 500 companies. Every deal was critical, and I used to read a lot of information about the client’s requirement to understand what key phrases in their requirements that we should build in our proposal that would attract immediate attention of the clients. Mainly, what problem the client is trying to solve, how to structure the solution and how to communicate this to the client and finally how do we budget the cost that is commensurate to the size and scope of the problem. The CEO won’t sign the proposal until I sign the proposal and explain why this proposal makes sense in a face-to-face meeting. That developed some strategic planning and thinking in my head over this incredible experience. It would be wrong to say that I succeeded all the time as we lost mostly 7 out of 10 proposals but 30% bid to win ratio was considered exceptional prior to year 2000. Then came the IPO challenge where I was part of the team to prepare the company for NASDAQ listing. It involved enormous effort to understand how to explain the business model in plain English so that common public can understand, and how to make the institutional investors buy into the business model. This experience enabled me to develop my skills in structural thinking. Then I was thrown into a new role of handling acquisitions. I had a Board Member joining the company full-time and he had extraordinary skills in M & A but won’t conduct a training for me as he believed only by experience only one can understand the business models of acquisition targets rapidly and assimilate the information to communicate internally. We had visited number of companies throughout the world and after such meetings, we used to have prolonged dinner meetings in which he would ask series of questions. I used to hate him for not saying what he needs to communicate. Later I realized that he was preparing me to think independently and structurally to write down the summary of everything we heard in a meeting. Mainly, he trained me to ask questions about things that are not covered in the meeting and find the cons of such acquisitions instead of pros. He trained me to watch body languages and the subjects that are quickly covered or skipped in the meetings so that we can focus those areas at the time of due diligence. Generally, it is always difficult to understand the thoughts of others but with structural thinking, it is possible to get close to such thoughts. It requires a skill that would get into the root cause of that thought and unfold the line of thinking. By doing this, once can save plenty of time in life. Even though I am 67 years old, and all those skills are dormant for a while now, the puzzle solving brought back those wonderful memories to the forefront. What are the key words, what is not being said, what the puzzle make is targeting to bring out, which are direct and indirect clues, what are the unspoken words of the puzzle maker, etc., in my opinion, rebuilds that structural thinking skills. I am sure software professionals have used this technique for building solutions for complex problems. I would like to hear how they used the structural thinking skills in their professional and personal life.