We scan new podcasts and send you the top 5 insights daily.
At a production robotics company, Aaron Moncur learned to interview engineers for technical needs and manufacturing directors for ROI before writing proposals. He answered executives' likely questions upfront, which improved his odds of getting projects approved and taught him the value of clear technical writing.
Don't just broadcast information to stakeholders. Use presentation time for discovery. Ask direct questions like "Is this relevant?" and observe body language to learn what truly matters to them. Each meeting is a chance to refine your understanding of their priorities for the next interaction.
Tailor your message by understanding what motivates your audience. Technical teams are driven to solve problems, while sales and marketing teams are excited by new opportunities. The core idea can be identical, but the framing determines its reception and gets you more engagement.
Don't just ask executives what they want to achieve, as this puts them on the spot. Instead, proactively formulate a hypothesis about their goals and challenges. Presenting this gives them a concrete starting point to react to, confirm, or correct, leading to much faster alignment.
Bupa's Head of Product Teresa Wang requires her team to explain their work and its value to non-technical people within three minutes. This forces clarity, brevity, and a focus on the 'why' and 'so what' rather than the technical 'how,' ensuring stakeholders immediately grasp the concept and its importance.
Instead of saying a CAD update took 10 hours, an engineer should explain how it reduced manufacturing defects or improved quality. Framing contributions in the "language of value" helps leadership and other departments understand the direct impact on business goals like revenue and cost savings.
Technologists often fail to get project approval by focusing on specs and data. A successful pitch requires a "narrative algorithm" that addresses five key drivers: empathy, engagement, alignment, evidence, and impact. This framework translates technical achievements into a compelling business story for leadership.
Miscommunication with non-technical stakeholders (finance, sales) is a common failure point. Engineers should take negotiation courses to frame technical problems in terms of business needs, do their research, and present a case effectively to get buy-in.
Structure your final presentation by calling out specific problems you learned from individual contributors by name. Then, immediately pivot to show how solving their problem directly contributes to the high-level business objective owned by the executive decision-maker. This makes every stakeholder feel heard and demonstrates their strategic value.
To get faster internal buy-in, create a custom AI agent trained on a key stakeholder's past feedback from notes, messages, and document comments. Run new proposals through this 'skill' to frame them in a way that resonates with their priorities before they even see them.
To communicate effectively with leadership, treat them as a customer persona. Research their problems, needs, aspirations, and communication style. This allows you to frame your proposals as solutions to their specific challenges, ensuring your message lands effectively and moves initiatives forward.