The Engineering of Insight: Six Frameworks to Organise Your Communication
- Michael Walker and AI

- Jan 29
- 7 min read

We often mistake good communication for good vocabulary. We think that if we use impressive
words or perfect grammar, our message will land. The reality is quite different. In the professional world, clarity creates impact, and clarity is rarely about word choice. It is about structure.
When you receive a rambling email or sit through a disjointed presentation, the frustration you feel is not usually caused by the content itself. It is caused by a lack of organisation. The sender has transferred the burden of sorting information onto you. They have given you a pile of bricks and asked you to build the house yourself.
One thing good communicators do is treat communication as an engineering problem rather than an artistic one. They use established frameworks to organise their thoughts before they type a single word. This approach respects the reader’s time and ensures the message survives the noise of the modern workplace.
Here are six organising principles that will help you structure your communication for maximum impact. And further down you will find AI prompts based on each principle.
Bottom Line Up Front (BLUF)
The US military developed this concept to ensure that orders were understood immediately, even in high-stress environments. In the corporate world, it is the antidote to the "mystery novel" style of writing where the main point is buried in the final paragraph.
BLUF requires you to state the most important information in the very first sentence. This is not a summary or an introduction. It is the conclusion. You tell the reader exactly what you need from them or what the final decision is before you provide the context.
This feels uncomfortable for many people. We are conditioned to show our working. We want to list the data we analysed, the meetings we held, and the alternatives we considered before revealing our recommendation. We do this to prove we have done the work. Mostly, however, the reader does not care about your journey. They care about the destination.
When you use BLUF, you allow the reader to process the subsequent details with the correct context in mind. If you tell a manager "we are delaying the launch by two weeks" in the first line, they can read the rest of your email looking for the specific reasons and mitigation plans. If you save that news for the end, they spend the entire time reading your email wondering where it is going.
The 4A Structure
While BLUF is excellent for quick updates, you sometimes need a more robust structure for presentations or longer proposals. The 4A framework provides a narrative arc that moves an audience from a state of passivity to action.
The four components are Attention, Agenda, Argument, and Action.
Attention is the hook. You must solve the problem of why the audience should listen to you right now. This is not about being entertaining. It is about relevance. You state a shared problem or a significant opportunity that affects the people in the room.
Agenda creates a roadmap. This aligns with the principle of "tell them what you are going to tell them". It reduces anxiety in the room because the audience knows exactly what to expect.
Argument is the core of your message. This is where you provide your data and your reasoning. Because you have already secured their attention and set the agenda, the audience is mentally prepared to process this information.
Action is the close. You must be explicit about what happens next. A presentation that ends with "thoughts?" is a failure of structure. You should end with specific requests or next steps.
Deloitte Business Chemistry
Structure is not effective if it ignores the person receiving the information. The Deloitte Business Chemistry framework acts as a guide for tailoring you’re the information you are communicating to specific personality types. It suggests that your audience likely falls into one of four categories, and each requires a different structural approach.
Drivers are logical and competitive. When writing for them, your structure must be minimal. Use BLUF aggressively. Bullet points are your friend. Do not include a "background" section unless they ask for it.
Guardians are methodical and risk-averse. They value data and process. If you send a Driver-style email to a Guardian, they will think you are reckless. For a Guardian, you must structure your communication to show your methodology. You need a section that explains how you reached your conclusion and what risks you have mitigated.
Pioneers are creative and big-picture thinkers. They get bored by the heavy process that Guardians love. Your structure for a Pioneer should emphasise the vision and the future possibility before getting into the weeds.
Integrators focus on relationships and consensus. Your structure needs to include the human element. You should organise your message to highlight how different stakeholders are affected and who has been consulted.
What? So What? Now What?
This is perhaps the most versatile framework for status updates and project briefs. It forces you to bridge the gap between raw data and practical application.
"What?" covers the facts. This is the objective reality of the situation. For example, website traffic is down by 10%.
"So What?" explains the implication. This is the part most people miss. They assume the data speaks for itself. It rarely does. You must explicitly state why this matters. In this case, traffic is down by 10%, which means we are projected to miss our lead generation target for the quarter.
"Now What?" proposes the next step. You must move from the implication to a solution. We need to increase our spend on paid search for the next three weeks to bridge the gap.
If you only provide the "What", you are just a news reporter. When you add the "So What" and "Now What", you become a strategic advisor.
PREP (Point, Reason, Example, Point)
The PREP framework is designed for persuasion. It is particularly useful for impromptu speaking or when you need to make a strong case in a short email.
You start with the Point. This is similar to BLUF. You state your opinion or recommendation clearly. "I believe we should switch to the new software vendor."
You follow immediately with the Reason. This explains the logic. "The current vendor has raised prices three times in two years while their support times have slowed down."
You then provide an Example. This grounds your logic in reality. "Last week, the marketing team was unable to access the platform for four hours, and it took support two days to respond."
Finally, you restate the Point. "For these reasons, switching to the new vendor is the right move."
This structure works because it is self-contained. It is a tight loop of logic that is difficult to argue with because the evidence is sandwiched securely between the main claims.
The STAR Method
While the previous frameworks are about looking forward or managing the present, the STAR method is the best way to organise information about the past. It is often used in job interviews, but it is equally powerful for performance reviews, project retrospectives, and case studies.
STAR stands for Situation, Task, Action, Result.
Situation sets the scene. You describe the context so the reader understands the difficulty of the challenge.
Task defines your specific responsibility. What were you meant to achieve?
Action is the most critical section. You must describe what you actually did. A common mistake here is using the passive voice or saying "we" too much. This structure demands that you specify the steps you took to solve the problem.
Result is the payoff. You must quantify the outcome. "Ideally, you should use numbers here. It is not enough to say the project went well. You need to say it saved the company 15% in operational costs."
Using STAR prevents you from rambling about your hard work without ever proving its value. It forces every story to have a satisfying conclusion.
Structuring Prompts for AI Assistance
Artificial Intelligence is only as good as the instructions you give it. If you ask a Large Language Model (LLM) to "write an email about the project delay," it will likely give you a generic, waffle-filled response.
To get the best results, you should use these organising principles as constraints in your prompt. This forces the AI to think like an engineer.
Here are specific prompts you can use to apply these six principles to your drafting process.
The BLUF Prompt
"I need to write an update to my manager. Please rewrite the draft below using the BLUF (Bottom Line Up Front) format. The most critical piece of information is [insert key point]. Ensure this is the very first sentence, and group all supporting context afterwards."
The 4A Prompt
"I am giving a presentation on [topic]. Please outline my speech using the 4A structure (Attention, Agenda, Argument, Action). For the 'Attention' section, suggest a hook that relates to [specific audience pain point]. For the 'Action' section, ensure there are three clear bullet points for next steps."
The Deloitte Prompt
"I need to explain a technical risk to a stakeholder who is a 'Driver' personality type (focused on speed, logic, and results, dislikes heavy process). Rewrite the technical explanation below to suit this persona. Remove necessary jargon, keep it brief, and focus on the impact rather than the methodology."
The What? So What? Now What? Prompt
"I have the following data points about our Q3 performance: [insert data]. Please structure a status update email using the 'What? So What? Now What?' framework. For the 'So What?' section, explain the business impact of these figures. For the 'Now What?' section, propose a logical course of action based on the trends."
The PREP Prompt
"I need to convince my team to [insert decision]. Please write a short script for me to say in a meeting using the PREP (Point, Reason, Example, Point) framework. My main point is [insert point]. My main reason is [insert reason]. The example I want to use is [insert example]."
The STAR Prompt
"I am writing my self-appraisal for the year. I need to describe my work on [Project X]. Please draft a paragraph using the STAR (Situation, Task, Action, Result) method. Here are the raw details of what happened: [insert messy notes]. Ensure the 'Result' focuses on the quantitative outcome."
Conclusion
There is a misconception that using frameworks makes your writing robotic. People fear that if they follow a structure, they will lose their personal voice. The opposite is usually true. When you remove the clutter and the confusion, your actual ideas have room to breathe.
Your colleagues are overwhelmed with information. They are drowning in unread messages and back-to-back meetings. When you take the time to organise your communication using one of these principles, you are doing them a service. You are signalling that you respect their time and that you are in control of your subject matter.
The next time you sit down to write, stop looking for the perfect word. Look for the perfect structure. The clarity will follow.





Comments