Strategies For Presenting Engineering Projects

A few days before the deadline, I’d find myself in that familiar pool of anxiety : staring at a blank digital canvas, clock ticking, knowing the next 20 hours would dissolve into a blur of bullet points, chart creation, & late-night pixel-alignment. Time to make a presentation. With AI, I’ve slashed the time it takes to build a presentation from a full day down to just a few hours. I start with the essence - three key ideas or stories that will resonate with my audience. With these seeds planted, I’ll dictate to the AI to architect a 12-slide framework, calibrated for its audience (recently, sharing predictions for data in 2025 to a group of data engineers & analysts which I’ll publish next week). They are The Great Consolidation, Scale Up Architectures & Agentic Data. I suggest a few deeper points like new query engines, virtual developer environments, separation of compute & storage, & collaborative BI. Then I ask the AI to draft the speaker’s notes in a framework that my management coach at Google taught me - the “Clearing-Content-Transition” framework: Clearing: Describe what’s on the slide Content: Detail 3-4 key points & supporting stories Transition: Set up the next slide naturally Each iteration refines the narrative. “Move slide 5 to after slide 10.” “Shorten the section on AI & engineering teams fusing.” “In scale up architectures, there’s a generational transition where many of the new engineers prefer Python. Weave that in.” The outline evolves as AI & I collaborate. We craft a surprising hook (no more “Hi, my name is…”), from Matthew Dick’s storytelling wisdom to give audiences a reason to care by introducing the Stakes. With the outline nearly complete, the next step is to add the visual flair. “Please create a prompt for an image in for each slide.” This part isn’t yet automated, but I flipped back and forth between the prompts and an image generation AI. Put it all together, deliver it online, read from the script a few times to practice so the delivery is a bit more spontaneous and it’s done and dusted. Not every image or every slide can be fully automated, but many of them can. There’s something about starting a blank canvas with an AI that solves or at least bevels the edges of writer’s block. I’ll publish the presentation on Jan 24. I’ll also publish the script alongside it & would love to hear your reactions.

����One mistake I made in my early interviews was failing to present my projects clearly. I knew the work inside out, but I couldn’t explain it in a structured way — and that cost me opportunities. Over time, I realized that interviewers aren’t just looking for what you built, but how you communicate your impact. Here’s a framework that can help you explain any project with clarity: 🔹 Context / Background Start with a quick snapshot of the project. What was the situation? Why was the project important? Keep it concise, something you can explain in under a minute. 🔹 Problem You Tackled Highlight the exact challenge. What issue did you or your team face? Why was it worth solving? This sets the stage for your contribution. 🔹 Your Contribution Be specific about your role. Did you design, code, test, lead, or optimize? Talk about key tasks you handled, roadblocks you hit, and how you overcame them. 🔹 Solution Approach Walk through how you solved the problem. Break it down into steps so the interviewer can follow your thought process — from the initial idea to the final execution. 🔹 Tools & Tech Mention the technologies, frameworks, or methods you used. This shows your technical decision-making ability and how you apply the right tools for the job. 🔹 Results & Outcomes Quantify the impact if possible. Did you improve performance by 30%? Save the team hours of work each week? Secure positive client feedback? Numbers and concrete results make your contribution stand out. 🔹 Collaboration & Learning Close by talking about teamwork and personal growth. How did you coordinate with others? What new skills did you pick up? What would you approach differently if given another chance? ✅ Remember: An interview isn’t just about what you built — it’s about showing your ability to identify problems, craft solutions, and communicate them clearly. #InterviewTips #CareerAdvice #ProjectShowcase #SoftwareEngineering #InterviewPreparation #CommunicationSkills #TechCareers #ProblemSolving

As engineers we are really good at being technical... 👇🏼 Dependency injection, TDD, Clean Code, Reverse Proxies… we are all in. But there’s something simpler but harder we struggle with... And it’s makes you standout when interviewing, and looking to grow as an engineering leader (senior and beyond roles). Taking on challenging, high-impact projects. AND. Quantifying those project wins to business outcomes and wins. 🧠 We are technical superstars, so what often happens internally in conversations, or when interviewing is we go deeeep into the technicalities. “I rebuilt our build system from webpack 1.x to webpack 4.0 and removed the x/y/z security vulnerability, and speed up load times significantly.” Sounds impressive… But for product, business, and hiring leaders, it’s hard to really understand how valuable and impactful that was. What if instead for the same project, you were able to say: “I identified that our build system had several security vulnerabilities. I also discovered it cost our engineers 125 hrs / month waiting for builds to complete. I spearheaded an effort to upgrade this system, and led the team to fix our security issues, and decrease build times by 78%. Combined these measures saved our business approx $150,000 / yr.” Ok now you have their interest… they can’t wait to dive in more and ask follow up questions and learn more about the project. 🔥 But how can you get stories like that? Brag docs. – Keep a daily log of project updates + learnings. – Summarize these into meaningful impact every 2 weeks. – Summarize those wins again every 2-3 months into top wins/learnings. – Quantify them. Talk with engineering, business and product leaders to get the bigger picture and some impact numbers. – Use these wins/learnings in resumes, performance reviews, interviews, etc. Taking on challenging projects is key to your success. Don’t stop there. Quantify and document those wins. ✔️ - - - - - - - - - - - - - - - - - - - - - - - - - - - - If you liked this post, you’ll probably love my weekly newsletter: https://lnkd.in/e95JH9qH

Getting the opportunity to present on big stages at conferences is easier if you have a plan. During a 1:1 with a leader on my team, she brought up that some team members want to present at large user conferences such as re:Invent and AWS Summits. However, those speaking slots are very hard to obtain and usually go to speakers with proven sessions—ones that have been presented multiple times and have solid ratings. I'm not only a public speaker but also serve as a Speaker Bar Raiser, coaching others on public speaking and presenting. I've delivered dozens of sessions at large events worldwide and learned valuable lessons about getting ideas onto big stages. (Spoiler alert: It isn't enough to submit an abstract and hope for the best) It seems like a Catch-22, but there is a process that can tilt the odds in the aspiring speaker's favor. Content - Ensure your content is new, unique, relevant, insightful, timely, and/or important to your target audience. Irrelevant content is a non-starter. Structure - Have a framework for presenting the content that makes it easy to follow and understand. There is a science behind using the "Rule of Three" in public speaking. Keep things simple and interesting. Repetition - Give your presentation as many times as possible. Ask to present at brown bag lunches, weekly team calls, stand-alone learning sessions, your local Toastmaster's club meetings—even to your family and friends. After each presentation, ask for feedback and explore other presentation opportunities. These "at-bats" will improve your speaking skills and provide valuable feedback to enhance your session. (Hint: when presenting to larger groups, ask them to complete a survey capturing CSAT data. You can use this later when submitting for the biggest stages) Refine - Use all feedback to improve your presentation and make it more impactful. Collect notes from audience members and look for ways to incorporate their suggestions. If a joke or anecdote doesn't land, try something else. If your closing statement falls flat, take a different approach. Continuous iteration leads to improvement. Marketing - Once you have a relevant topic that you can present in a structured format, refined and updated through multiple presentations, you'll still need to market it effectively to track owners. Share data about your presentation frequency, CSAT scores, and audience testimonials. Don't let rejection discourage you—keep going until you get a "Yes." Developing and following a plan like this will help increase your chances of getting on big stages, more often.

🛡️ How To Defend And Explain Your Design Decisions. With strategies to protect your work, avoid design by committee and pick battles wisely ↓ 🚫 Avoid big surprises when presenting your work. ✅ Ask for feedback gradually, at different stages of the design. ✅ Strong decisions rely on data and research, not hunches. ✅ Attach your decisions to a goal, metric, or a problem. ✅ Show what’s possible short term, and your plan for the future. ✅ Re-iterate business goals before showing any of your work. ✅ Show the process that led you to your current design. ✅ Explain how your current decision impacts business goals. ✅ Highlight key takeaways from previous rounds of feedback. ✅ Highlight advantages and risks to show they’ve been considered. 🚫 Don’t fight an argument: find the problem brought into spotlight. ✅ You might be wrong: defend the project goals, not your work. ✅ Ask to articulate and explain the argument in detail. ✅ Have alternatives ready, and explain why they were discarded. ✅ Defer the decision: request to review it with your team. 🚫 One suggestion is a goldmine of other ideas waiting to be excavated. Good design isn’t about being the winner in the big meeting. It’s about finding the flaws and wrong assumptions to make sure your work matches business goals while supporting user’s needs. So be deliberate and meticulous explaining how your decisions impact business goals. Nothing diffuses argument like agreement. Don’t get defensive — as Tom Greever noted, when we become defensive, we fail to focus on the real issues. So avoid big public debates. Avoid speaking about your personal preferences, what you like or dislike. Don’t ask “What do you think?” as it prompts personal opinions. Instead, ask if attendees agree with the direction (yes/no), and if not, why not. Most importantly, defend your design decisions when you know it’s right, but leave your ego aside when you feel you aren’t. And: as Femke van Schoonhoven highlighted, knowing the goal is critical, but keep in mind that the goal can change. New insights will influence the goal and the direction of the project, and we have to recognize them and move forwared — and not get hung up on a particular idea or goal that’s since been abandoned. Useful resources Defending UX Design Decisions, by Chris Kiess https://lnkd.in/erMUpKj8 The Tyranny of Collaborative Ideation, by Lars Jerichau https://lnkd.in/e-JGNqNN Articulating Design Decisions, by Tom Greever 👍 https://lnkd.in/efmNb2Mr Articulating Design Decisions to Stakeholders, by Uxcel https://lnkd.in/evKXsP3e Strategies To Deal With Design By Committee, by Jennifer Lee https://lnkd.in/evacmmHd #ux #design

Team presentations are hard to pull off. Most look like disconnected mini-talks. Having coached 10,000+ leaders from 50 countries, 2-3 people presenting is a common challenge:   👎 Speakers are not aligned 👎 Transitions are clumsy 👎 The person not speaking looks bored Instead you want to show alignment, clarity, and collective authority.  Here’s how to make sure your team speaks as one: 1/ Align on your message ↳ Before creating slides, get clear on the shared objective ↳ Ask: What should the audience know, feel, and do? 2/ Create a “plan on a page” together ↳ Agree on structure, outline and who does what.  ↳ If it is a 3-act structure, one person may do 1 and 3, the other part 2. 3/ Define the depth and detail ↳ Who goes deep? Who stays high-level? ↳ Only do deep and high-level, avoid the mediocre middle ground. 4/ Corporate or casual? ↳ Bring the same energy. ↳ Coordinate appearance and tone. 5/ Sharpen your speaker transitions ↳ Don’t say, “Now I am passing over to Sophie.” ↳ Say: “Now that we’ve seen the challenge, Sophie will walk you through our solution.” 6/ Don’t kill the flow with confusion ↳ Agree in advance who drives the slides and practice together. ↳ Agree on a subtle gesture; don’t say “Next slide, please”. 7/ Stay engaged — even when not speaking ↳ Look at the speaker or audience, not your shoes ↳ If you are not fully engaged, why should the audience be? 8/ For virtual teams ↳ Meet 5min early to test tech and slides. ↳ Keep energy up — Zoom fatigue is real. 9/ Plan your Q&A strategy ↳ Decide who answers what type of question ↳ Assign a “conductor” to manage flow and timing In a team presentation, every role matters. Get the content right. Get the transitions right. Get the Q&A right. - - - - ♻️ Repost to help others and follow Oliver Aust for more. ♟️ Want to become a top 1% communicator? Reach out here: https://lnkd.in/eRy_qSUq

I didn't turn up to my presentation for Deutsche Bank and AnitaB.org. I prepared the slides. I put a lot of thought into why each and every tip was important. Yet at the end of the day, I wasn't there... I was sick 🤢 Still, their loss is your gain, because I've turned everything from that presentation into a blog post for your convenience! 🥳 In it, I cover the core of presenting technical concepts and/or digitalisation proposals to non-technical stakeholders. SPOILER: it's more about listening and watching than it is about convincing! Here's the summary for those not wanting to read the whole thing: 🧐 Speak their language: ask about existing knowledge and establish what 'level' the stakeholder wants to speak at. No need to jump into architecture if they only want to know about personnel requirements. 😳 Cater to the lowest level in the room: Try to modify your explanations so that everyone gets it. Even those with more technical experience can learn from hearing a non-technical explanation. 🤩 Focus on collaboration and co-creation: Don't view it as a pitch, but rather as a chance to design a solution together. Be open to "teach don't preach" if they do look for more details. 👏 Be direct about resistance: Communicate options, and interpret resistance as an opportunity to put their minds at ease or to design a different solution together. 🤫 Practice active listening: 'Listening' sometimes happens with the eyes, not the ears. Look for moments when people tune out, change topics, or fidget more. You're losing your audience! 🚙 Use metaphors: Bridges, factories, post offices, architecture, and housing construction have all been metaphors I have used for explaining software engineering concepts to non-technical stakeholders. 🧙🏻♀️ Incorporate storytelling: Where possible, use real-world stories to illustrate processes, for example on how software engineering teams work using agile approaches, or versioning control. 😎 Be their resource: View these talks as the start of your relationship beyond this specific project. Position yourself to be their 'go to tech person' when they need something clarified. --- What do you think? #engineeringmanagement #technicalcommunication #strategiccommunication #pitching https://lnkd.in/eNQ5stUW

Presenting is one of those skills that catches a lot of consultants off guard. They know their material and have years of real experience behind them. But the moment they step into a room, the dynamics change. I see the same issues show up again and again: The equipment isn’t set up the way it should be. The lighting makes it hard to see the slides. The room layout works against the message. And once the presentation starts, filler words, dense slides, or unclear transitions make it difficult for clients to stay with them. None of this means they aren’t capable. It simply means the presentation wasn’t set up for success. Over the years, I’ve developed a set of principles I teach my consultants to help them avoid these pitfalls. Here are eight of them: Own Your Equipment and Environment Don't rely on anyone else for equipment or supplies. Arrive early to test and confirm everything is working. Tell a Client-Relevant Story Use a short story that mirrors your audience's challenges. Problem, solution, impact. Ditch Dense Slides Have one concept per slide. Minimal text. If people are reading, they're not listening. Make Numbers Meaningful Translate data into something real. Don't say "12% attrition." Say "1 in 8 team members is leaving each year." Use the Rule of Three Structure your message around three key points. Our brains love patterns. Rehearse Like a pro Great presenters look spontaneous, but every word and beat is rehearsed. Practice your timing, pauses, and transitions. Strengthen Delivery and Clarity Be intentional with your language and avoid filler words that weaken your credibility. Create a “Wait for It…” Moment Save one insight, reveal, or recommendation for near the end. Pause before delivering it. Make it unforgettable. Strong presenters don't wing it. They prepare, simplify, and deliver intentionally. If your presenting skills are already strong, and you're figuring out your next step to grow, I built a quiz to help. It gives you a personal report of your consulting archetype and a roadmap of what to do next. You can take the quiz for free here: https://lnkd.in/gve8CjUu What would you add to this list? 📨 If you're ready to book a call send me a DM with the word "ready." ♻️ Repost this to help out your network. ➕ Follow Dale Gibbons to turn your genius into a 7-figure consulting business.

7 Steps To Present Ideas Executives Can't Ignore: (The framework that wins approval every time) Even genius ideas fail without proper framing. The right sequence transforms skeptics into sponsors. Master this sequence to get executive buy-in: 1. The Problem: ↳ Start with business issues executives care about ↳ Example: "40% slower growth than competitors" 2. Compelling Cost: ↳ Quantify inaction in metrics they track ↳ Example: "$4.7M lost revenue this quarter alone" 3. Root Issues: ↳ Present 2-3 structural drivers from research ↳ Example: "Product covers only 60% of needs" 4. Solution Principles: ↳ Get agreement on "must-haves" before your idea ↳ Example: "No new headcount, 9-month ROI" 5. Proposed Approach: ↳ Connect high-level solution to agreed principles ↳ Example: "Expand 3 product categories strategically" 6. Implementation Path: ↳ Show clear phases with early wins ↳ Example: "Validation complete in first 30 days" 7. Resource Needs: ↳ Be specific about exactly what you need ↳ Example: "2 current engineers, $50K market testing" If you're struggling with executive buy-in, give this a try. What framework has worked best for your presentations? ♻️ Repost to help others get their ideas approved. 🔔 Follow me for more strategy execution frameworks.

Congratulations! You have been accepted to speak at your first major engineering conference...and you are not prepared... Here are a few Stage Mom tips to get you on the right path: 🙋♀️ Remember to honor your accepted abstract - this will be your north star for definition of done. 🙋♀️ You may feel the need to do an information overload, but this will defeat your ultimate goal of leaving audience with some key takeaways. Let your fear of ego go and simply let others know to follow you on LinkedIn for more resources (have QR code at beginning and end). 🙋♀️ Treat each slide as a mini-talk and state key takeaway at end to help audience (and yourself transition to the next slide and/or highlight anything that may have been missed). 🙋♀️ Show the code or prompting steps! GIFs/screenshots can be super helpful audience. 🙋♀️ People remember the beginning and end of your talk the most. Make sure that you have a coherent narrative at the beginning and repeat at the end. Your keytakeaways is not your dumping ground for items that didn't fit into talk, but a clear wrap to overall message. 🙋♀️ Memes and GIFs are fun and when used effectively, a great engagement for audience. But please use sparingly and also consider how some may be received (i.e. cultural context). 🙋♀️ When you try to please everyone, you please no one, including yourself. Remember who your primary target audience for the talk is and deliver value there. 🙋♀️ Context setting is important, but if you have spent half of your talk doing just this, you are wasting others time. 🙋♀️ If you are going to have a text heavy slide (try to avoid), use animations for columns or bullet points so folks do not get ahead and will stay with you. 🙋♀️Do dry-runs with your trusted Stage Moms ahead of time and always share in version that they can comment on before live dry-run. These are just a few Stage Mom tips, but felt important to share. Public speaking is a gift and so is the value that you can bring to others. Invest the time in delivery and go be awesome. #Engineering #PublicSpeaking #ProfessionalDevelopment