Hello,
Welcome to another episode of learning from Chris Fenning’s book, The First Minute. In the previous episodes, we explored the concept of framing and how to structure the beginning of a conversation using three elements: context, intent and key message. Today, we are moving on to the next chapter, where the author introduces another communication technique called Structured Summaries.
Fenning explains that many workplace conversations involve discussing challenges, identifying what we want to achieve and determining how best to move forward. These challenges may relate to projects, processes, people or everyday responsibilities. While the framing technique is useful for introducing a conversation or communicating a brief message, longer discussions, such as presenting a proposal, giving project feedback or addressing a team, require a structure that helps us communicate our thoughts clearly without losing our audience. This is where Structured Summaries come in. The author introduces a three-part method consisting of Goal, Problem and Solution.
Understanding the GPS Method
He explains that once we move beyond socialising and casual conversations, much of what we discuss at work involves solving problems and overcoming challenges. Organisations have goals, targets and deadlines, and a significant part of our responsibilities involves ensuring that these are achieved.
These challenges vary in complexity. They may be as simple as running out of office supplies or struggling to get time with someone from another department. They may also involve a team failing to meet its key performance indicators, an entire customer support system going down, or securing a major contract and putting everything in place to deliver on it. Regardless of the nature of the problem, we need to communicate it in a way that others can understand. And this brings Fenning to an important point: our workplace conversations should not simply focus on describing problems; they should focus on finding solutions.
He identifies three common situations we encounter when discussing work-related problems. First, we may have identified a problem but need someone else’s help to find a solution. Second, we may have identified the problem and already have a solution that we want to recommend. Third, we may have encountered a problem, resolved it and now need to report the outcome. These situations are different, but they all require us to communicate the goal, the problem and the solution clearly. This is the foundation of the GPS method: Goal, Problem and Solution.
He explains that this structure is particularly useful when communicating with larger audiences. Think about a presentation where you are speaking to more than thirty people. It is easy for your audience to lose track of what you are trying to communicate, especially when you spend too much time explaining the background or history of a project without clearly establishing what you want to achieve, what is standing in the way and how you intend to address it.
The three-part method helps prevent that by giving your conversation a clear direction.
The Goal: This is what you want to achieve. It is the outcome you are working towards or the objective you want your audience to understand. In other words, before discussing the challenges or possible solutions, you need to establish what you are trying to accomplish.
The Problem: This refers to the obstacles, challenges or difficulties that are preventing you from achieving your goal. These are the things standing in the way of the outcome you want to achieve. The author also makes an important distinction between the goal and the problem, because these two can easily be confused. The goal is what you want to achieve, while the problem is what is making it difficult to achieve it.
The Solution: Once you have established the goal and identified the problem, you can then communicate the solution. This is what you intend to do to address the challenges or remove the obstacles that are preventing you from reaching your goal.
For example, imagine that you are a manager addressing your team about improving the delivery of a particular project. You would begin by explaining the goal, which is to complete and deliver the project within the agreed timeframe. You would then identify the problem, perhaps explaining that delays in receiving materials are affecting the project’s progress. Finally, you would present the solution, which could involve reviewing the procurement process, engaging suppliers earlier or implementing a system to monitor material availability.
The author explains that this method can be applied to several professional situations, including giving feedback on projects, presenting proposals, discussing challenges with your team and communicating plans as a manager. Rather than allowing the conversation to become a long explanation filled with background information, you keep bringing it back to the goal, the problem and the solution.
No Problem Is Too Complex to Summarise
At this point, you may be wondering whether the GPS method can really work for complex topics involving several variables, departments, technical processes or multiple dependencies. Surely, some problems require more than three sentences to explain? Fenning addresses this concern with an example involving two NASA engineers, Santosh and Doug, who were discussing the continued funding needed to maintain the International Space Station. They explained the various challenges involved, including radiation, fuel, transporting people and supplies, and the dangers posed by debris in space.
After listening to their discussion for some time, Nick, who had no engineering background, asked why the station was so expensive to maintain. The engineers spent more than twenty minutes explaining the technical details. When they finished, Nick summarised what he had understood using the GPS approach: the goal was to build a science laboratory in space; the problem was that getting there and keeping people alive was extremely difficult; and the solution was to provide sufficient funding to maintain the station and ensure the scientists’ safety.
What makes this example interesting is that Nick was able to communicate the central issue without having the technical knowledge of the engineers. His explanation was simplified, of course, but it addressed what his audience needed to understand: why maintaining the space station was so expensive. This brings us to an important lesson: your explanation should be appropriate for your audience. You do not need to share every detail you know about a subject to communicate its main point. The goal is to give people enough information to understand the issue, while recognising that a more technical audience may require a more detailed explanation.
We spend so much time explaining how we got to where we are that we forget to communicate where we are trying to go and what needs to happen next. The GPS method reminds us to keep those important points at the centre of the conversation. So, the next time you are preparing a presentation, giving feedback or discussing a challenge at work, consider these three questions: What are we trying to achieve? What is preventing us from achieving it? And what are we going to do about it?
I hope this gives you another practical tool to consider in your professional communication.
Thank you for reading.

Leave a Reply