Streamlining Internal Communications

Are you still polling your backend every few seconds just to get updates? That’s not just inefficient — it’s a terrible user experience. In my latest video, I walk you through how to implement real-time communication in .NET using SignalR. We’ll build an order tracking system that sends live updates from the backend to the frontend. ✅ Configure SignalR in .NET ✅ Build and secure your Hub ✅ Target specific users using User() ✅ Secure it with JWT ✅ Update the UI instantly via WebSocket Oh, and I’ll also show you how to make your SignalR client methods strongly typed — cleaner code, fewer bugs. Watch the full tutorial here: https://lnkd.in/e6hH5gak If you’re building modern web apps with ASP .NET Core - this is a must.

"We're moving forward with another vendor." Every rep's nightmare sentence. I pressed for details. "Their approach felt more open. We actually knew what we were buying into." That stung. I'd shared: ••• Exhaustive feature documentation ••• Dozens of success stories   ••• Complete pricing breakdowns Where'd I go wrong? Days later, I got access to our competitor's sales process. The difference hit instantly: They didn't preach transparency. They lived it. Their follow-up wasn't an email avalanche. It was one collaborative hub where buyers could: ••• Monitor which stakeholders engaged with what ••• See their exact position in the evaluation journey ••• Find materials curated for their unique pain points ••• Manage internal distribution seamlessly My revelation: I was buried in PDFs. They were cultivating partnership. Next prospect, new approach: I built a shared workspace exposing EVERYTHING: → Which team members on our side viewed their data → Critical docs they'd missed → Realistic implementation expectations → Where we excel AND where we don't The buyer's response: "Finally, someone not playing games." Ink on paper in 10 days. Here's what's real: Today's buyers aren't starved for data. They're starved for authenticity. Yesterday's strategy: Bombard with polished assets that sidestep weaknesses. Tomorrow's strategy: Build transparent environments that tackle doubts directly. Your buyers know when something's off. Even when nothing is. Quit running sales like a shell game. Start running it like a glass house. You with me?

I know it is a new month, and many are scrolling through their phones looking for inspiration to push through the final stretch of the year. But I want to pause and address something that has been on my mind for a while. Too often, when young professionals are asked for progress, the response is, “we’re working on it.” If you believe that is a professional answer to give, I'm sorry, but it is not. It communicates the opposite of what you intend. When someone asks for an update, they already assume you are working. What they need is clarity. What progress has been made? What challenges have you encountered? When can delivery be expected? A vague response signals avoidance, incompetence, or worse, a lack of accountability. If there is a challenge, state it clearly. If there is a delay, be proactive about it. If things are on track, provide specifics. Keeping people you work with informed is not just good practice; it is how you build trust, reliability, and long-term credibility. The people who rise in their careers are not those who simply say they are working on it. They are the ones who take ownership, manage expectations, and communicate with transparency. Delete vague updates from your vocabulary. Own your work. Communicate with precision. That is how you stand out, and that is how you grow.

Small variations in prompts can lead to very different LLM responses. Research that measures LLM prompt sensitivity uncovers what matters, and the strategies to get the best outcomes. A new framework for prompt sensitivity, ProSA, shows that response robustness increases with factors including higher model confidence, few-shot examples, and larger model size. Some strategies you should consider given these findings: 💡 Understand Prompt Sensitivity and Test Variability: LLMs can produce different responses with minor rephrasings of the same prompt. Testing multiple prompt versions is essential, as even small wording adjustments can significantly impact the outcome. Organizations may benefit from creating a library of proven prompts, noting which styles perform best for different types of queries. 🧩 Integrate Few-Shot Examples for Consistency: Including few-shot examples (demonstrative samples within prompts) enhances the stability of responses, especially in larger models. For complex or high-priority tasks, adding a few-shot structure can reduce prompt sensitivity. Standardizing few-shot examples in key prompts across the organization helps ensure consistent output. 🧠 Match Prompt Style to Task Complexity: Different tasks benefit from different prompt strategies. Knowledge-based tasks like basic Q&A are generally less sensitive to prompt variations than complex, reasoning-heavy tasks, such as coding or creative requests. For these complex tasks, using structured, example-rich prompts can improve response reliability. 📈 Use Decoding Confidence as a Quality Check: High decoding confidence—the model’s level of certainty in its responses—indicates robustness against prompt variations. Organizations can track confidence scores to flag low-confidence responses and identify prompts that might need adjustment, enhancing the overall quality of outputs. 📜 Standardize Prompt Templates for Reliability: Simple, standardized templates reduce prompt sensitivity across users and tasks. For frequent or critical applications, well-designed, straightforward prompt templates minimize variability in responses. Organizations should consider a “best-practices” prompt set that can be shared across teams to ensure reliable outcomes. 🔄 Regularly Review and Optimize Prompts: As LLMs evolve, so may prompt performance. Routine prompt evaluations help organizations adapt to model changes and maintain high-quality, reliable responses over time. Regularly revisiting and refining key prompts ensures they stay aligned with the latest LLM behavior. Link to paper in comments.

**Fostering Growth Through Open and Transparent Feedback** 🚀 Today, I want to dive into a topic that's close to my heart: the power of open and transparent feedback in grooming talent. 🌱 In the fast-paced world we navigate, it's crucial to create an environment where feedback isn't just a formality, but a catalyst for growth. 💡 Transparent communication lays the foundation for a culture that nurtures talent, fosters collaboration, and propels individuals to reach their full potential. **1. Honesty breeds excellence:** Let's face it—constructive criticism isn't always easy to deliver or receive. However, it's the cornerstone of improvement. Embracing honesty in our feedback, whether it's positive or points out areas for development, is key to helping our colleagues evolve and excel in their roles. **2. Two-way street of communication:** Feedback isn't a monologue; it's a dialogue. Encouraging open conversations empowers team members to share their perspectives and insights. This two-way street not only promotes a sense of belonging but also ensures that feedback is a collaborative effort aimed at continuous improvement. **3. Specificity is the key:** Vague feedback often leads to confusion. Being specific about what worked well and what could be enhanced provides actionable insights. Whether it's acknowledging a job well done or pinpointing areas that require attention, specificity is the compass that guides individuals toward their professional best. **4. Timely feedback fuels progress:** Timing is everything. Providing feedback in real-time allows individuals to apply insights immediately, preventing the entrenchment of habits that may hinder their growth. Timely feedback is a catalyst for ongoing improvement and ensures that the learning curve remains dynamic. **5. Cultivating a growth mindset:** Open feedback culture is synonymous with cultivating a growth mindset. Encouraging team members to see challenges as opportunities for learning fosters resilience, adaptability, and a hunger for continuous development. In conclusion, a workplace that values open and transparent feedback is a breeding ground for talent development. It's not just about critiquing—it's about nurturing, guiding, and cheering on each other's success. Let's create environments where feedback isn't feared but embraced, where every comment is a stepping stone toward greatness. Together, we can elevate not just our individual careers but the collective success of our teams. #FeedbackCulture #TalentDevelopment #GrowthMindset #Collaboration #ProfessionalDevelopment #learninganddevelopment #feedbackculture #feedbackmatters #talentdevelopment

#100RulesofThumb — Rule 30 Always err on the side of providing more context than what you think is necessary. —— It's common to assume that what's obvious to you is also obvious to others. But this is rarely the case. As a rule, while communicating, always assume asymmetry in information. In other words, you should always assume that the other person knows less than you think they do about a given subject, context, or project. This isn't to belittle anyone's intelligence or experience; rather, it's a safeguard against the curse of knowledge. You see, once you get good at something, you forget what it's like to be a newbie. You're in marketing, and you think everyone knows what "CTR" or "ROAS" means. Trust me, they don't. And even if they do, you're usually better off assuming they don't while documenting stuff. Because you never know who is going to go through your documentation in the future. Don't assume; explain. Likewise, if you're running behind on a project, don't go radio silent. Tell your team what's up. A simple "Need another day, still grinding" goes a long way in keeping people's trust. When you assume symmetry — that is, when you think the other person knows what you know — you're setting the stage for misunderstandings. If you're a project manager and you assume that your team knows the project's background as well as you do, you might skip crucial details when assigning tasks. This will cause needless delays and errors. Or if a team member doesn't fully understand the problem you're trying to solve, they're less likely to come up with creative solutions. They might not even know how high the ceiling is for breaking the rules. And when things go wrong due to poor communication, it's not just the project that suffers. Team members may start to lose faith in each other and in the leadership, and we all know how that goes. Hence, always provide context when communicating. Whether it's an email, a meeting, or a one-on-one chat, make sure to include the 'why' and the 'what' along with the 'how.' Another slightly hard to implement idea: After you've communicated something, ask the other person to summarize what they've understood. This will quickly reveal any gaps in their understanding. Ambiguity charges high interest, and we all pay it in lost time and screw-ups. You want to be the person who cuts through the fog. Make things crystal clear, and you'll save everyone a lot of headaches. Also, when you provide more context, you're opening yourself up feedback. Maybe someone has a better idea or a quicker solution. Maybe they'll tell you to take a breather. Either way, you're better off than working in a vacuum. No one is going to punish you for being elaborate. So be elaborate and don't leave any space for obvious questions. In the long run, it will save you a lot of time in going back and forth on trivialities.

Interview Conversation Role: RTE in #SAFe Framework Topic: Preparation for PI Planning 👴 Interviewer : "PI Planning is around the corner. How would you ensure it's well-prepared and smooth for everyone involved?" 🧑 Candidate: "I’d make sure the teams know the agenda and are clear on their tasks." 👴 Interviewer: "Let’s add a layer. Imagine stakeholders have conflicting priorities, and teams are feeling unclear on dependencies. A lack of alignment could derail the PI. How would you structure your prep to tackle these challenges?" 🧑 Candidate: "I’d send out reminders about the PI objectives and ask teams to review their backlogs." What an effective Release Train Engineer should say: ---------------------------------------------------------- ✨ PI Planning success starts with comprehensive prep. I’d first facilitate a Pre-PI alignment workshop with Product Management, System Architects, and key stakeholders to clarify objectives and identify any competing priorities. This helps shape a single, clear vision for the PI. 💬 I’d then work closely with Product Owners and Scrum Masters to conduct a ‘Feature Readiness’ session to ensure all feature backlogs are prepared, dependencies mapped, and objectives aligned with our business goals. ✔ For example, in a previous ART, we held cross-team syncs in the lead-up week to discuss shared dependencies, which prevented delays and miscommunication during PI. 📊 Additionally, I’d ensure that the Solution Train and System Architects host architecture readiness sessions, providing teams with the necessary technical context. Any major risks or unknowns are surfaced early, allowing us to address them in a risk management session before PI Day. 🏹 Impact: With thorough preparation, everyone enters PI Planning focused, equipped, and aligned. This approach mitigates last-minute roadblocks, clarifies dependencies, and ensures that the ART can plan realistically, setting us up for a successful PI execution.

𝗛𝗼𝘄 𝘁𝗼 𝗕𝗿𝗲𝗮𝗸 𝗗𝗼𝘄𝗻 𝗦𝗶𝗹𝗼𝘀 𝗶𝗻 𝗠𝗲𝗱𝗧𝗲𝗰𝗵 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁: (𝗖𝗿𝗲𝗮𝘁𝗶𝗻𝗴 𝗰𝗿𝗼𝘀𝘀-𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝗵𝗮𝗿𝗺𝗼𝗻𝘆 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝘁𝗵𝗲 𝗵𝗲𝗮𝗱𝗮𝗰𝗵𝗲𝘀) Ever notice how Quality, R&D, Regulatory and Marketing teams seem to speak completely different languages? This disconnect isn't just frustrating, it's costing your medical device company time, money, and potentially regulatory approval In my personal experience, I've seen how departmental friction can derail even the most promising innovations 𝗧𝗵𝗲 𝗥𝗲𝗮𝗹 𝗖𝗼𝘀𝘁 𝗼𝗳 𝗦𝗶𝗹𝗼𝘀 👉 Delayed submissions and market entry 👉 Regulatory surprises late in development 👉 Documentation rework and compliance gaps 👉 Increased development costs 👉 Team frustration and burnout Here's how to create seamless collaboration across your MedTech organization: 𝗦𝘁𝗲𝗽 𝟭: 𝗘𝘀𝘁𝗮𝗯𝗹𝗶𝘀𝗵 𝗖𝗿𝗼𝘀𝘀-𝗙𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝗚𝗼𝘃𝗲𝗿𝗻𝗮𝗻𝗰𝗲 Create a development council with representatives from Quality, Regulatory, R&D, Manufacturing, Marketing and Clinical. Meet bi-weekly with a structured agenda (top tip keep the minutes to use towards management reviews). 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: A Class II device manufacturer implemented this model and reduced their development timeline by 30%, if not more, by identifying regulatory concerns during concept phase rather than pre-submission. 𝗦𝘁𝗲𝗽 𝟮: 𝗜𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁 𝗦𝘁𝗮𝗴𝗲-𝗚𝗮𝘁𝗲 𝗥𝗲𝘃𝗶𝗲𝘄𝘀 𝘄𝗶𝘁𝗵 𝗔𝗹𝗹 𝗦𝘁𝗮𝗸𝗲𝗵𝗼𝗹𝗱𝗲𝗿𝘀 Don't move to the next development phase without formal sign-off from every department. This prevents costly backtracking 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: During a stage-gate review (Design Review), a clinical specialist identified that the intended claims presented by the regulatory team would require further clinical data. By catching this early, the company adjusted their development plan rather than facing a surprise 6-month+ delay come submission time 𝗦𝘁𝗲𝗽 𝟯: 𝗖𝗿𝗲𝗮𝘁𝗲 𝗮 𝗦𝗵𝗮𝗿𝗲𝗱 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 𝗟𝗮𝗻𝗴𝘂𝗮𝗴𝗲 Develop a glossary of terms that bridges departmental jargon. This prevents miscommunication that leads to rework. 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: One client I worked with created a “MedTech Translation Guide” with input from each department. Not only did it reduce confusion, but it also built mutual respect engineers finally understood what the regulatory team meant by “intended use” and marketers stopped using terms that could trigger a knock on the door by Competent Authorities 𝗧𝗵𝗲 𝗕𝗼𝘁𝘁𝗼𝗺 𝗟𝗶𝗻𝗲? When this is done right, it accelerates development, strengthens compliance, and builds a more engaged team ✅ Faster to market ✅ Fewer compliance surprises ✅ Less internal friction If you're building your next-gen device and struggling with internal disconnects, it’s time to rethink how your teams work 𝘵𝘰𝘨𝘦𝘵𝘩𝘦𝘳 💬 I'd love to hear: How does your team keep cross-functional collaboration on track? #MedTech  #MedicalDevice #ProductDevelopment

Mastering virtual communication Being a strong communicator in a virtual world isn’t just an advantage; it’s a necessity. To help communicate with clarity, influence, and impact in an online world, PING offers a research-backed, practical framework: Perspective Taking Initiative Nonverbal Cues Goals 🚩 Digital communication strips away vocal tone and body language, often leading to unintended misinterpretations. When communicating digitally, be intentional about tone, clarity, and structure. Adding context, using emojis strategically and being explicit with intentions can bridge the gap. 🚩 Over-communicating doesn’t solve problem - intentional, well-structured communication does. Set clear agendas for meetings, use project management tools, and avoid unnecessary back-and-forth messages. 🚩 Delivering difficult news online requires a different approach - one that accounts for emotional impact, timing, and personalisation. If the conversation is high-stakes (layoffs, performance reviews, conflict resolution), don’t rely solely on email or a rushed video call. Use personalised communication, offer space for dialogue, and acknowledge emotions. 🚩 Strategic emoji use actually enhances engagement and prevents misinterpretation. Use emojis sparingly and strategically. A smiley in a casual message? Great. Overloading a business proposal with them? Maybe not. 🚩 Before scheduling a meeting, ask: Can this be handled asynchronously? If yes, save everyone time and send a well-structured message instead. High-emotion topics (conflicts, big decisions) → Video call Routine updates, data sharing → Email or message. 🚩 Employees don’t disengage because of workload alone; they disengage because they feel unheard in digital workspaces. Prioritise personalised check-ins and transparent communication. Set boundaries around digital overload. Andrew Brodsky | Professor at McCombs School of Business at The University of Texas at Austin 📚 Ping: The Secrets of Successful Virtual Communication #BetterEveryDay #Leadership