How to Foster Innovation in Data Teams

Pay close attention to the frequency of healthy debate, constructive challenge and openness to new and divergent ideas that takes place in your teams. If the frequency is low… …there is the risk of creating the illusion of performance because people readily ‘understand’ each other, agree on everything, collaboration seems to flow smoothly and there is a collective sensation of progress. However, the opportunity cost is teams gets trapped in their own paradigms, opportunities get overlooked, risks ignored - and ultimately their output becomes derivative not innovative, performance diminishes as opposed to improving and compounding. If the frequency is high… …there is a level of psychological safety that allows for team members to be more objective, to speak up with relevant ideas, to constructively challenge each other, and bring their diverse perspectives and experiences to the table - in the knowledge it won’t be held against them. This opens up the opportunity of reframing the paradigm, and connecting different perspectives and ideas. Ingredients for creativity, innovation, resilience and performance. You see homogeneous teams might feel easier, but easy doesn’t translate into Performance. Here are a few ideas to experiment with your teams… 1. Intentionally foster a team environment that replaces scepticism with intellectual curiosity, an open and learning mindset.   2. Consider how you can create a ways of working that allows all ideas and perspectives from everyone in the room to be heard. 3. Encourage dissenting perspectives. Surrounding yourself with people who are willing to disagree with you and challenge your perspectives and each other. 4. Consider whether you may need to invite others to that creative or idea generation meeting to ensure you get a broader perspective. 5. De-stigmatise failure through sharing past mistakes and celebrating lessons learnt. 6. Institutionalise a team culture of healthy candour. Candour is one of the key attributes to improving the quality of output, levelling up creativity and enabling effective collaboration. What would you add? 👇🏽 #culture

In tech, everyone talks innovation. But the real game-changer? Creating a team that isn’t afraid to fail ↓ My biggest edge in scaling tech teams? I borrowed it straight from IO psychology. It's the lever nobody talks about: Psychological safety. In the fast-paced world of tech, where innovation is king, we often overlook the human element. A team that feels safe to take risks is a team that innovates. How do you create this environment? 1. Encourage open dialogue 2. Celebrate failures as learning opportunities 3. Lead by example - admit your own mistakes 4. Reward vulnerability and honesty 5. Foster a culture of constructive feedback When team members feel psychologically safe, they're more likely to: - Share innovative ideas - Take calculated risks - Collaborate effectively - Learn from failures - Adapt to change quickly The result? A more agile, creative, and productive tech team. This approach has helped me build high-performing teams that consistently deliver groundbreaking solutions. Remember: Technology is our tool, but people are our greatest asset. Invest in your team's psychological safety and watch your innovation soar. Create an environment where your tech talent can truly thrive.

As a data professional one thing you may be tasked with is helping drive a culture that embraces data. Culture and the people in an organization can hinder data work if they aren't wanting to utilize data, lack understanding around data, or are fearful. How can we help to excite and ignite the data work in an organization? One key thing you can do is to help generate curiosity in your organization and allow that to ignite innovation and use of data. Remember, the majority of the employees in an organization aren't data professionals by trade or title. Helping employees to embrace data can be difficult but you have the opportunity to help them succeed with data. Curiosity is a catalyst to data and AI work. How can we help to drive more curiosity in your organization? First, we need to foster a culture where we question things. As a data professional, help people to develop a pattern and habit of asking questions. What else can be done to help foster curiosity? ✅ Teach that experimentation is welcome. Allow people to share ideas and experiment on these ideas. ✅ Teach that you don't fail but you learn. As Nelson Mandela said: I never lose. I either win or learn. ✅ Free up people's time to do deep work. Allow or encourage people to block off 30 minutes a day to explore and learn. Teach that this time should be free from email, Teams or Slack, and text. Create an environment where critical thinking is encouraged. ✅ Provide access to resources. If we want non-data people to get excited about data we should provide resources for learning. ✅ Celebrate discovery and innovation. Celebrate questions, ideas, wins. ✅ Ask open-ended questions and encourage people to go and find answers. Overall, curiosity can ignite data work so allow it to do so. As a data professional lead the way and don't allow your own thoughts or ideas to block others. Foster the right culture. Stay nerdy, my friends #dataliteracy #AIliteracy #datastrategy #AIstrategy #data #AI #curiosity

Want to retain your top data talent? Let me share what I've learned from years of building Microsoft data teams. It's not perks or fancy titles, it's day-to-day leadership. I've noticed that technologists stay loyal to leaders who make them feel truly valued. Here are 10 proven ways to build trust and performance without micromanagement: 1. Give Credit Publicly, Share Credit Privately → Let your data teams shine. Recognition drives retention. 2. Invite Them to Challenge Assumptions → Ask "What am I missing?" Data teams thrive on honest dialogue. 3. Fund Personal Experiments → Provide Fabric trials, GPT API keys, or innovation time. 4. Celebrate Data Wins → Query optimisations deserve as much recognition as business wins. 5. Offer Teaching Moments → Enable junior devs to present at sprint reviews. 6. Ask About Career Direction → Help map their path to CTO or Microsoft MVP roles. 7. Normalise Not Knowing → "Let's figure it out together" is powerful leadership. 8. Encourage External Learning → Support conference speaking and community engagement. 9. Trust Them with Decisions → Especially on architecture and security choices. 10. Admit When You're Wrong → It creates psychological safety and trust. If you're leading a data team and want to discuss implementing these principles, let me know in the comments. I'd love to hear which one works for you. #DataLeadership #MicrosoftFabric #PowerBI If you found this content valuable, share it with your network ♻️ and follow me for more insights!

Let's talk about something I've observed being frequently overlooked in a businesses data strategy - the power of diverse perspectives in how we approach, interpret, and utilise our business data. Too often, businesses fall into the trap of viewing their data through a single / narrow lens - typically that of the data team or a specific functional. Here's the thing, your marketing team sees different patterns than your sales team. Your product teams spot trends that your technology team might miss. Your finance department's interpretation of the same metrics could reveal insights that operations never considered. I've learned that the real opportunities in data are discovered when you create environments where these different viewpoints can collide. It's not just about having the data - it's about fostering a culture where multiple perspectives can challenge assumptions, spot hidden opportunities, and identify blind spots in the analysis. Think about it, how many potential innovations or solutions have been missed because we limited who gets to ask questions of our data? How many insights have gone undiscovered because we stuck to conventional interpretation and operating frameworks? The key is building frameworks that actively encourage and capture these diverse viewpoints. This means: 🪂 Breaking down data silos between functions 🪂 Creating cross-functional data SME's 🪂 Establishing processes where different functions can regularly share their unique data insights 🪂Training teams to look beyond their immediate objectives when analysing data 🪂 Creating and maintaining tangible links between data and business context The future belongs to businesses that can harness the full spectrum of perspectives within their walls. What are you doing to ensure your data tells it's complete story? #DataStrategy #BusinessIntelligence #Innovation #Leadership #Diversity #Analytics #CognitiveDiversity

Yesterday I talked about the innovation standoff in multifamily. Today, this one's for the operators. You're not anti-innovation. You're anti-disaster. After watching pilots fail and "game-changing solutions" create more work than they solved - your caution isn't resistance. It's wisdom. But the operators who crack the code on piloting effectively won't just adopt innovation. They'll shape it. Here's the playbook: 1. Create a dedicated innovation budget that survives budget season. Not "we'll find money if something comes up." A protected line item. When you have to beg for pilot funding, you've already lost momentum. 2. Rethink the roles you need. The operators winning in 2026 are investing in: → AI/Automation leadership → Innovation program management → Change management specialists → Data & intelligence resources You can't bolt innovation onto people already drowning in their day jobs. 3. Fix your site selection strategy. Stop giving pilots your most broken properties. That property has staffing problems, deferred maintenance, and a team barely keeping their heads above water. The PropTech company walks into a hurricane and is expected to prove sunshine. Give pilots a property with a stable team, an on-site champion who wants to participate, and leadership that's bought in - not burned out. 4. Build your data lake. This doesn't eliminate integrations - you'll still need them. But when you control your data centrally: → You're not waiting on a PMS to prioritize your needs → Clean data makes new integrations faster → You validate solutions with YOUR data before committing → You negotiate from strength, not dependency That's sovereignty. Sovereignty accelerates innovation. 5. Align success metrics BEFORE the pilot starts. What does "success" look like? What KPIs? Who's measuring? Get this in writing. Both sides. Skip this step, and you'll end the pilot with PropTech claiming victory while your team says "it didn't work" - and you'll both be right. 6. Build in executive sponsorship. Pilots without C-suite air cover die. Not because leadership kills them - but because no one protects them from budget cuts and competing priorities. 7. Incentivize innovation at every level. Build it into performance reviews. Build it into promotion criteria. Celebrate pilots - even failed ones - because you learned something. 8. Design the exit strategy upfront. When there's no graceful off-ramp, people avoid getting on the road entirely. Make "this didn't work and here's what we learned" an acceptable outcome. The infrastructure for innovation is just as important as the innovation itself. Build the playbook. Then run the plays. Tomorrow: What PropTech companies need to do differently to earn the pilot. What would you add to this playbook? What's worked at your organization?

Transformation stalls when teams wait for instructions. In my work helping enterprises scale innovation and capability, I see one recurring bottleneck: A culture of "Workers" instead of "Strikers." If your team stops as soon as a task is finished, your transformation project will likely stall. To move the needle in today's workplace, leaders must mentor for Workplace Intelligence. Here is how I coach teams to move from task-takers to high-impact drivers: Move from "Task" to "Next Step": Don't just accept a report. Demand that the sender highlights the focus areas and verifies the data integrity. Coach the "Why" When a team prepares a report, mentor them to ask: "What decision does this drive?" If they don't know the goal, they can't add value. Institutionalize "Solution-First" Thinking: Stop accepting problems at your desk. Require that every roadblock comes with Options A, B, and C. Your job as a leader is to choose the path, theirs is to pave it. Demand Clarity over Guessing: Create a culture where "Confirmation of Understanding" is the norm. Assumptions are the most expensive overhead in digital transformation. Build Poise: High-stakes innovation requires clear thinking under pressure. Reward the "I will investigate and report back" response over the "panicked ramble." The bottom line for Enterprise Leaders: Innovation isn’t just about the right toolkit; it’s to focus on the quality of execution. If you don't intentionally coach "Strikers," you are simply managing a queue of tasks. How are you evolving your team's Workplace Intelligence to meet disruption? #DigitalTransformation #InnovationStrategy #LeadershipDevelopment #paulinea