Virtual Innovation Collaboration

💎 60 UX Strategy Methods And Activities (Figma) (https://lnkd.in/eCDU-vhR), a large repository of UX methods, templates and activities for ideation sessions and product sprints, from storyboards and brainwriting to 6 thinking hats, journey mapping and concept testing. Neatly put together in one single place by fine folks at Merck. The team has also put together a very thorough overview of their UX Strategy Kit (https://lnkd.in/ek5dEYn4), broken down by categories for strategy, observation, ideation and warm-up, along with detailed video walkthroughs, examples and step-by-step guides. Frankly, most of these methods are unfamiliar to me. And by no means is the point to actually study and apply all of them. What works for you works for you. To strategize, I rely on How Might We but also think about metrics that should be moved once we implement some features or refine some user flows. For event storming and brainstorming, I tend to rely on Bono’s 6 thinking hats to align brainstorming, and (of course) journey mapping. For ideation, I love using storyboards to jump right into the user’s success story, but would also use card sorting with cut-out paper cards to understand user’s mental model. And for almost every project, I’d run concept testing with tree testing or Kano model, or low-fidelity/paper prototyping to understand if we are on the right track. Once you sprinkle a bit of critical thinking, early user testing and strategic planning across the design work, you gain confidence that you are moving in the right direction. And really that’s all you need. A few of my personal bookmarks with UX methods and activities: UX Tools For Better Thinking, by Adam Amran 👏🏽 https://untools.co/ Playbook For Universal Design (+ PDF/Powerpoint templates) https://lnkd.in/ernris4g UX Methods & Projects, by Vernon Fowler https://lnkd.in/eAHaiaSm 18F Method Cards https://methods.18f.gov/ Hyperisland UX Methods Resource Kit 👍 https://lnkd.in/eDTaci7T How To Design Better UX Workshops, by Slava Shestopalov https://lnkd.in/edxqCC-n How To Run UX Workshops With Users, by yours truly https://lnkd.in/ejm7_TsS Happy designing, everyone — I hope you’ll find these guides and resources helpful to get started. Just don’t feel like you have to try out all of them. It might be much more worthwhile to get early feedback from stakeholders and end users, even if your work isn’t really “good” enough. Good luck! #ux #design

The National Institute of Standards and Technology (NIST) has released a draft of its “Cybersecurity Framework Profile for Artificial Intelligence” (open for public comment until Jan 30, 2026) to help organizations think about how to strategically adopt AI while addressing emerging cybersecurity risks that stem from AI’s rapid advance. Building on the #NIST Cybersecurity Framework 2.0, the Cyber AI Profile translates well-established risk management concepts into AI-specific cybersecurity considerations, offering a practical reference point as organizations integrate AI into critical systems and confront AI-enabled threats. The Cyber AI Profile centers on three focus areas: • Securing AI systems: identifying cybersecurity challenges when integrating AI into organizational ecosystems and infrastructure. • Conducting AI-enabled cyber defense: identifying opportunities to use AI to enhance cybersecurity, and understanding challenges when leveraging AI to support defensive operations. • Thwarting AI-enabled cyberattacks: building resilience to protect against new AI-enabled threats. The Profile complements existing NIST frameworks (CSF, AI RMF, RMF) by prioritizing AI-specific cybersecurity outcomes rather than creating a standalone regime.

𝟏𝟎 𝐂𝐲𝐛𝐞𝐫𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐅𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤𝐬 𝐌𝐨𝐬𝐭 𝐓𝐞𝐚𝐦𝐬 𝐈𝐧𝐡𝐞𝐫𝐢𝐭 - 𝐍𝐨𝐭 𝐂𝐡𝐨𝐨𝐬𝐞 ! A big customer asks for SOC 2. A regulator mentions ISO or NIST. Suddenly your “strategy” becomes a messy stack of rules that nobody can clearly explain. Frameworks were meant to reduce confusion. Not multiply it. Here’s the truth 👇 If you remove the logos, most cybersecurity frameworks answer the same few questions: – What are we protecting, and how critical is it? – Which controls reduce real attacks first? – How do we prove trust to customers and regulators? – How do we improve over time instead of ticking boxes once? That’s it. The 𝟏𝟎 𝐦𝐚𝐣𝐨𝐫 𝐟𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤𝐬 simply sit at different points of that map. Some shape strategy: ➤ NIST CSF gives structure and direction Some formalize governance: ➤ ISO 27001 / 27701 turn security into a certifiable system Some drive action: ➤ CIS Controls tell engineers where to start Some build external trust: ➤ SOC 2, PCI DSS, HIPAA, HITRUST speak auditor language Some go deep where risk is highest: ➤ CSA CCM, NIST 800-53, 800-171 for cloud and government needs 𝐓𝐡𝐞 𝐦𝐢𝐬𝐭𝐚𝐤𝐞? Treating frameworks like competing religions. Strong 𝐭𝐞𝐚𝐦𝐬 𝐬𝐭𝐚𝐜𝐤 𝐭𝐡𝐞𝐦. One shapes strategy. One drives execution. One proves trust. Over time, the question changes from: “𝐀𝐫𝐞 𝐰𝐞 𝐜𝐨𝐦𝐩𝐥𝐢𝐚𝐧𝐭 𝐰𝐢𝐭𝐡 𝐗?” To: “𝐖𝐡𝐢𝐜𝐡 𝐦𝐢𝐱 𝐛𝐞𝐬𝐭 𝐞𝐱𝐩𝐥𝐚𝐢𝐧𝐬 𝐨𝐮𝐫 𝐫𝐢𝐬𝐤 𝐬𝐭𝐨𝐫𝐲 𝐭𝐨 𝐭𝐡𝐞 𝐩𝐞𝐨𝐩𝐥𝐞 𝐰𝐡𝐨 𝐦𝐮𝐬𝐭 𝐭𝐫𝐮𝐬𝐭 𝐮𝐬?” That’s when frameworks stop being paperwork and start acting like an operating system for security. Which framework actually helps your team make better decisions today? 👇 Which one does your organization rely on most right now? ------------ Hi, I'm Harris D. Schwartz 𝐅𝐫𝐚𝐜𝐭𝐢𝐨𝐧𝐚𝐥 𝐂𝐈𝐒𝐎 𝐚𝐧𝐝 𝐂𝐲𝐛𝐞𝐫𝐬𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐋𝐞𝐚𝐝𝐞𝐫. I help CEOs and executive teams strengthen their security posture and build resilient, compliant organizations. With 𝟑𝟎+ 𝐲𝐞𝐚𝐫𝐬 𝐚𝐜𝐫𝐨𝐬𝐬 𝐍𝐈𝐒𝐓, 𝐈𝐒𝐎, 𝐏𝐂𝐈, 𝐚𝐧𝐝 𝐆𝐃𝐏𝐑, I know how the right security decisions reduce risk and protect growth. If you are planning how your security program needs to evolve in 2026, this is the right time to have that conversation. #CyberSecurity #SecurityFrameworks #RiskManagement #CISO #ISO27001 #NIST #SecurityStrategy

Stuck in a rut? Does coming up with a good idea feel like picking something to watch on Netflix? (every choice is mediocre, you end up arguing/scrolling for 2 hours) I have a few ‘good ideas’ to help. Here are 4 brainstorming techniques for UX problems. 💡 🧠 The HMW Reframing Method Start with a challenge—users aren't completing sign-up. Now, reframe it as a How Might We question—how might we make sign-up irresistibly easy? This simple switch kickstarts solution-oriented thinking.  Pro tip: Generate multiple HMWs for each problem to explore different angles. 🧠 The Intersection matrix Create a grid with user needs on one axis and random objects or concepts on the other. For example, "Quick checkout" meets "Rollercoaster." How could the thrill and speed of a rollercoaster inform your checkout process? It's weird, agreed. But you never know, you might end up with unexpected brilliance. 🧠 Reverse brainstorming Flip the script. Instead of asking "How do we improve user engagement?", ask "How could we completely destroy and annihilate user engagement?" List all the terrible ideas, then reverse them. It's a fun way to identify pain points and generate solutions you might have overlooked. 🧠 The 5 Whys You know this classic. Basically, become a toddler. Start with a problem statement and ask "Why?" five times. Each answer becomes the basis for the next "Why?" This helps you dig deeper and uncover root causes. For example: - Users aren't using the new feature. Why? - They don't know it exists. Why? - We haven't promoted it effectively. Why? - Our notification system is broken. Why? - It wasn't properly tested before launch. Why? - We rushed the development process. Boom. Now you know where to focus your problem-solving efforts. It also helps to begin ideation with the ‘hair on fire’ problem. Here’s how. https://bit.ly/4dHyjWl Let’s do opposites. What’s a brainstorming exercise you hate, and why do you think it doesn’t work? Looking to find some interesting answers in the comments! 🥸

The Case of the Costly Error Once upon a time, a critical bug in a bustling software company was reported in their flagship product just days before a major release. Panic spread through the team like wildfire. The bug was complex, and time was running out. At first, the team tried the usual approach—frantic debugging and patching. But the bug kept reappearing like a stubborn ghost. As deadlines loomed closer, frustration mounted. That's when Jane, one of the senior developers, stepped in. She suggested a different approach: structured problem-solving. She gathered the team in a meeting room and laid out a plan: 01. Define the Problem: They dissected the bug, identified its specific behaviors, and defined the problem statement clearly. 02. Collect Data: They gathered data on when the bug occurred, what actions triggered it, and the system conditions at that moment. 03. Generate Hypotheses: The team brainstormed potential causes, generating multiple hypotheses. 04. Test Hypotheses: They systematically tested each hypothesis individually, isolating variables and gathering more data. 05. Analyze Results: Based on the data collected, they analyzed the results of each test and eliminated hypotheses that didn't hold up. 06. Implement Solution: Finally, they identified the root cause and implemented a solution that fixed the bug once and for all. The bug was squashed, and the release went off without a hitch. What could have been a disaster turned into a valuable lesson. Structured problem-solving saved the day! → When faced with a daunting challenge, don't rush into solutions. Take a structured approach. #dhandhekafunda ps: Structured problem-solving approach acts as a compass when you are not emotionally trapped in the situation. If you are, have another competent individual take the lead. At least be that structured ;)

For over 20 years, I’ve coached Fortune 500 CEOs. Along the way, I’ve sat in thousands of meetings, boardrooms, off-sites, and virtual calls that should have been emails. Here’s what I’ve learned: most meetings fail before they even start. Not because people aren’t smart or the agenda is wrong. Because the collaboration happens in the wrong place. Here are four shifts that will transform how your team meets. 1. Move the debate before the meeting. The best teams don’t show up to learn and debate for the first time. They show up having already been briefed and weighed in asynchronously, in shared documents, with real thinking on the table. The meeting becomes a decision room. 2. Shrink the room. Not everyone needs to be there. If someone’s contribution is already captured in the pre-work, free them. Smaller rooms move faster. They also talk more honestly. 3. Assign dissent. Consensus is comfortable, but it’s also dangerous. The highest-performing teams I’ve coached assign the team to provide challenges. Not to be difficult, but to make the final decision stronger. 4. End with commitments, not summaries. Most meetings end with a recap of what was said. That’s useless. End with who owns what and by when. Clarity beats closure. If you do these four things, your meetings won’t just feel better. They’ll actually produce results.

Neurodiversity 101: Making meetings more neuroinclusive Meetings are meant to bring people together to share ideas, make decisions, and build connection. Yet, for many neurodivergent colleagues and often for others too meetings can be overwhelming, confusing, or simply unproductive. Have you ever been to a meeting and wondered why you were there or what was expected of you? Whether online or in person, more inclusive meetings benefit everyone. They create clarity, structure, and safety for diverse thinkers to contribute meaningfully. Here’s how to make meetings more neuroinclusive: 1. Clarity before you start Share the purpose, agenda, timing, and who’s attending where possible in advance. Make clear if attendance is optional or essential and what preparation, if any, is expected. Sending materials early gives everyone time to process and plan. 2. Structure supports inclusion Outline how questions will be handled and what turn-taking looks like. Minute key actions and share them promptly. End by explaining what happens next. Predictability reduces anxiety and ensures accountability. Be aware of the 'quiet ones' in the room and ensure everyone can participate. 3. Inclusive communication Use clear, plain language avoid “acronym fests.” Pause regularly to check understanding and invite clarification. Remember, silence doesn’t mean disengagement; some people need more time to formulate ideas. Some people may need time after the meeting to come back with their responses too. 4. Online inclusivity Show participants how to use platform features like captions, transcripts, or chat. Encourage written contributions and offer the option to keep cameras off to reduce sensory load/allow movement/ or just not seeing your own face all the time! Provide recordings or transcripts afterwards so people can review at their own pace. 5. Make space for every voice Avoid putting people on the spot. Allow time after the meeting for those who prefer to reflect before responding. Remember: the “quiet ones” may hold the most valuable insights. **Small changes, big impact Microaggressions — such as dismissing someone’s idea or using “humour” that excludes can and do erode trust. Inclusion grows when meetings feel psychologically safe and respectful. Neuroinclusive meetings are not just a “nice to have.” This is a universal design concept in action. They are cost-effective, efficient, and fair improving engagement, retention, and creativity. When everyone can contribute in their own way, we get better decisions and stronger teams. 🟣 Inclusion isn’t about changing people. It’s about changing the conditions so people can thrive. Can you add any other ideas of what works too?

Productivity means nothing if you’re running on empty. Slow down before you break down.   If work takes all your time, so will burnout. You don’t need more hours, you need better balance. How to achieve balance between productivity and play:   1. Time-block work and play. ⏰ ↳ Plan your day in blocks. ↳ Set alarms to switch tasks. Avoid overworking.   2. Use the “Big 3” rule. 🎯 ↳ Pick 3 must-do tasks daily. No long to-do lists. ↳ Finish those first. Everything else is extra.   3. Follow the 50/10 work cycle. ⏳ ↳ Work for 50 minutes. No distractions. Deep focus. ↳ Break for 10 minutes. Walk, stretch, or relax.   4. Create a shutdown routine. 🚦 ↳ End work at the same time daily. Close your laptop. ↳ Plan tomorrow’s top tasks. Then unplug fully.   5. Single-task like a pro. 🔄 ↳ Multitasking kills focus. Do one thing at a time. ↳ Batch similar tasks. Emails, calls, or admin together.   6. Work with energy, not just hours. ⚡ ↳ Do hard work when energy is highest. ↳ Save low-focus tasks for later. Keep momentum.   7. Move every hour. 🚶 ↳ Stand, stretch, or take a short walk. Avoid stiffness. ↳ Blood flow = focus. 8. Say 'no' more often. ✋ ↳ Every yes takes time. Be selective. ↳ Set clear boundaries.   9. Make rest a non-negotiable. 😴 ↳ Lack of sleep kills productivity. Prioritise it. ↳ Rest isn’t wasted time. It fuels deep work.   10. Optimise your workspace. 🏡 ↳ A tidy space = clear mind. ↳ Use music or silence. Find what boosts focus.   11. Celebrate small wins. ✅ ↳ Track your progress daily. Small steps add up. ↳ Reward yourself for effort. Not just big results.   Work and play aren’t opposites. Balance them, and you’ll do both better.   What’s your best tip for balancing work and life? Let me know in the comments.   ♻️ Repost to inspire work-life balance 👉 Follow Lauren Murrell for more like this

Remote work challenge: How do you build a connected culture when teams are miles apart? At Bunny Studio we’ve discovered that intentional connection is the foundation of our remote culture. This means consistently reinforcing our values while creating spaces where every team member feels seen and valued. Four initiatives that have transformed our remote culture: 🔸 Weekly Town Halls where teams showcase their impact, creating visibility across departments. 🔸 Digital Recognition through our dedicated Slack “kudos” channel, celebrating wins both big and small. 🔸 Random Coffee Connections via Donut, pairing colleagues for 15-minute conversations that break down silos. 🔸 Strategic Bonding Events that pull us away from routines to build genuine connections. Beyond these programs, we’ve learned two critical lessons: 1. Hiring people who thrive in collaborative environments is non-negotiable. 2. Avoiding rigid specialization prevents isolation and encourages cross-functional thinking. The strongest organizational cultures aren’t imposed from above—they’re co-created by everyone. In a remote environment, this co-creation requires deliberate, consistent effort. 🤝 What’s working in your remote culture? I’d love to hear your strategies.

Building High-Performance Remote Engineering Teams is not just about video calls.... I’ve worked with teams across the UK, Europe, and the US, and one thing is clear: remote work isn’t inherently slower. But a lot of engineering teams fail because they try to run distributed teams like co-located ones. Here’s what really makes a remote engineering team high-performing: 1️⃣ Communication by Design, Not by Chance Async-first: Chat isn’t enough. Document decisions, architectural diagrams, and API contracts in a place everyone can access. Structured updates: Daily standups are optional; status tracking through PR reviews, automated CI pipelines, and project boards is mandatory. 2️⃣ Ownership & Clear Boundaries Each engineer owns services, APIs, or modules end-to-end. Service contracts are explicit. Teams don’t block each other because ownership is clear and dependencies are well-documented. 3️⃣ CI/CD Is Non-Negotiable Remote teams must trust that pushing code won’t break production. Automated testing, linting, and deployment pipelines reduce friction and async bottlenecks. Feature flags and incremental rollouts are your best friend. 4️⃣ Knowledge Visibility Remote teams fail when knowledge lives in heads. Maintain internal wikis, architecture maps, and runbooks. Code reviews aren’t just for QA—they’re the primary async learning tool. 5️⃣ Metrics That Actually Matter Velocity in story points? Fine. But measure deploy frequency, mean time to recovery, bug escape rate, and codebase health metrics. These metrics highlight systemic issues instead of punishing individuals. 6️⃣ Tech Stack Choices Matter Prefer tools that support async collaboration: GitOps, Slack with integrated threads, Jira/Trello boards, distributed logging, observability dashboards. Avoid systems that require constant synchronous attention or centralised knowledge bottlenecks. 7️⃣ Culture Is Explicit, Not Implicit High-performing remote teams share principles in writing: “We merge only green builds,” “We document before we ship,” “We pair when ownership overlaps.” Bottom line: Remote engineering success is built on process, ownership, tooling, and visibility, not on heroic effort or long hours. If your team is still treating async work like a co-located office, you’re leaving productivity and sanity on the table.