Hybrid Project Management Methods

Most organizations want more collaboration. Fewer know specifically why and that ambiguity is usually the reason the efforts to build it do not hold. This is the starting point for any serious attempt to increase teamwork across an organization. Clarity about where collaboration is actually needed, how it creates value in that specific context, and what would be lost if it did not improve. Without that clarity, the actions taken tend to be generic culture programmes, team-building exercises, values statements and the results tend to be correspondingly shallow. When you have that clarity, the research points to a set of levers that work. All of them, not one or two. People: teams with higher average levels of agreeableness tend to be more cooperative. Hiring and developing for this matters. Leaders who support change and model learning have the power to drive team culture more effectively than almost any structural intervention. Tasks: framing work as genuinely interdependent so that each person can see how their contribution connects to the whole makes cooperative behaviour more likely and attracts more cooperative people over time. Recognition: at the point where bonuses, promotions, and assignments are decided, the behaviours that are rewarded shape the culture more directly than any stated value. If collaboration is not being actively recognised at those moments, the culture will not sustain it. And one finding from the research on multi-team systems that I find particularly important is coordination among leaders across teams matters more than coordination within individual teams for overall system performance. In other words, get the leadership layer aligned on goals and values and then give the operational teams the autonomy to execute. Trying to coordinate directly at the operational level is actually counterproductive. The collaboration challenge is a leadership challenge. It starts, and is sustained, at the top. #Collaboration #TeamPerformance #LeadershipCulture #OrganisationalBehaviour #RandallPeterson

“Work from Where You Work Best” Works for Us at Tough Day. This isn’t just a policy. It’s how we actually work, every day. We’ve got teammates in Argentina, Brazil, Colombia, Spain, and several cities across the US. Different time zones, different cultures, different work styles. Here’s what makes it work: 1. Clear Alignment We use the V2MOM invented by Salesforce's Marc Benioff – which stands for Vision, Values, Methods, Obstacles, and Measures – to help us all stay on the same page about where we’re going, how we’ll get there, and what success looks like when we do. 2. Team Agreements We facilitate dialogue about how we all work best as individuals up front. We negotiate and make these expectations clear from the start on any project team. That includes sharing a whole host of holidays that we can all celebrate! Happy Independence Day, Argentina! 3. Daily Stand-Ups No matter where we are, we make time for short daily check-ins. Each day has a designated theme and leader (Macro-Monday, Tech Tuesday, Waxing Wednesday...). The structure helps us stay in sync, talk through any issues, and help each other. 4. Intentional In-Person Time We don’t have a central office. Instead, we meet up for the kind of collaborative activities that are more productive in person. We time these in-person working sessions around other live events like client meetings or conferences. For us, it’s a much better investment than paying for office space. 5. AI-Native Collaboration AI is a valuable part of our team, and to state the obvious – AI doesn’t physically sit in the office (at least not yet for most of us). AI is our virtual co-worker. If you work with AI, you're already working remotely. But maybe the best part? This way of working requires us to be deeply thoughtful in our interactions. We are curious. We listen better. We learn from and leverage each other — across languages, locations, and backgrounds. And all of these behaviors make us stronger in everything that we do.

❓ What are some best practices for leading a virtual project team? Virtual teams can present unique challenges. How do we keep everyone aligned and engaged when our only connections are remote? Here are some practical tips for leading a virtual project team: 📢 Set Communication Ground Rules: Don't leave communication to chance! Is it Teams or Slack for quick questions, email for formal updates, or a project management platform for task assignments? Specify which tools to use for what types of communications. You should also encourage team members to share their working hours and availability to help manage expectations. 🎯 Optimize Virtual Meetings: Long, rambling virtual meetings can kill engagement, so ditch the round-robin status updates. Instead, use your meeting time for brainstorming, problem-solving, and decision-making. To create space for open discussion and feedback, share agendas ahead of time and incorporate interactive elements like breakout rooms and shared whiteboards. 🧩 Encourage Team Member Collaboration: Suggest that small groups of team members meet outside of regular team meetings to tackle specific tasks or problems together. These working sessions can help build trust and individual bonds. 👋 Schedule Individual Check-Ins: Schedule short, regular meetings with each team member to check in on progress, address challenges, and offer support. These meetings help to cultivate connections but also allow us to catch obstacles and potential delays early. Leading a virtual team requires intentional effort and clear communication. By implementing these best practices, you can foster a more collaborative environment, no matter the distance. #projects #projectmanagement ________________ 👋Hi, I'm Jami, a project management and planning consultant for mission-driven organizations. I write about my work and share strategies and advice for leading more impactful projects, teams, and planning. Follow me 🔔, comment 💬, and reach out ✉️ to keep the conversation going.

After 1,000+ leadership interviews, one theme stands out: Team brilliance dies when leaders solve alone. One client's team told me they stopped sharing creative ideas because they believed their leader already had a plan and only that plan would "win." This raises a question: When we say "collaborate," do we mean co-creating solutions or just offering input before we decide? While co-created solutions drive better outcomes, 34% of organizations say their leaders aren't ready for this shift. (Deloitte, 2023) In today's boundaryless workplace, co-creating solutions isn't just good culture; it's a business imperative. So what gets in the way? Gatekeeper tendencies can quietly creep in when we: ⇢ Hijack conversations with our ideas ⇢ Suck the energy out of team problem-solving ⇢ Diminish others' sense of contribution Try these 4 practices to shift toward collective brilliance: ⇢ Notice when you're in "editor mode" instead of "explore mode" ⇢ Create structured opportunities for others to lead ideation ⇢ Ask "What could that look like?" when new ideas emerge ⇢ Clarify what collaboration really means in your culture Gatekeeping doesn't protect your value. It prevents your team from reaching theirs. Where might you be unintentionally closing the door on brilliance? ♻️ If this resonated, repost to spark more collaborative leadership where it's needed most. 👋🏾 I am Michelle Awuku-Tatum. I share ideas on human-centered leadership, team dynamics, and company culture. Tap the 🔔 to follow along.

Here’s my “Weekend Musings” for May 17th, focused on the power and value of fostering a collaborative culture to drive high impact and high performance. Having led multiple teams over the years, I’ve observed two distinct leadership styles - those that thrive on conflict, and those that cultivate collaboration. I firmly advocate for the latter, except in specific contexts like Governance Vs Delivery roles. High-performance cultures are forged not through uniformity, but through the integration of diverse, often conflicting viewpoints. True collaboration leverages disagreement as fuel for innovation and impact. A 2017 Harvard Business Review study found that teams with “moderate task-related conflict” performed best, if psychological safety was present. Google’s Project Aristotle confirmed this: psychological safety ranked above intelligence or experience in predicting team success. Building psychological safety in teams and building in oneself is both a science and an art; also through structured mental models. This is a topic for some other day :). Here are some interesting ancient Lessons in Collaborative Power: Delian League (5th Century BCE): Post-Persian Wars, Athens led a coalition of Greek city-states to protect against future invasions. Despite tensions, Athens coordinated naval strategies and resource sharing. This uneasy alliance launched a cultural golden age—proof that aligned incentives can overcome rivalry. Mauryan Empire (4th Century BCE): Chandragupta and his advisor Chanakya, with vastly different styles, built a vast Indian empire. Their collaboration fused idealism with strategy. The Arthashastra, born from this union, emphasized statecraft, diplomacy, and negotiation—principles still used in geopolitical thinking. Roman Republic Senate: Despite ideological clashes, Rome institutionalized dissent. During the Second Punic War, intense debates between Scipio Africanus and conservative senators led to bold strategies that defeated Hannibal. Structured disagreement built resilience and long-term power. Modern Insights At NASA, engineers and leadership clashed over safety vs. timelines during the Apollo missions. Yet shared vision unified them. Cross-functional collaboration reduced technical failures by 30% from Apollo 11 to 17. Likewise, McKinsey (2021) found that companies with high collaboration are 20–25% more likely to lead in innovation. Practical Conflict-Positive Strategies 1. Anchor to mission over egos. 2. Foster empathy through cross-role exposure and projects. And demonstrate empathy by having high situational awareness. 3. Build trust: 86% of executives (Salesforce, 2020) cite poor collaboration as a cause of failure. 4. Reward collective views Vs lone wolves. Ancient empires and modern teams alike show that success lies in disciplined disagreement, shared goals, and trust-driven cultures. And always role model and recognize collaborative leaders. Reward them and inspire others. #Leadership

Helping your team identify their core values is essential for building a strong, cohesive, and aligned group. Here's how I've done it based on my experience: 1. Open Discussions: Start by having open and honest conversations with your team. Ask questions like: "What matters most to us as a team?" and "What principles should guide our actions?" 2. List Common Themes: Encourage your team to share their thoughts and ideas. As they speak, jot down common themes or recurring words that come up. This helps identify potential core values. 3. Prioritize Values: Once you have a list, ask your team to prioritize the values they believe are most important. You can use a voting system or a ranking exercise to do this. 4. Discuss Scenarios: To make values more tangible, discuss real-life scenarios where these values come into play. For example, if "Integrity" is a potential value, talk about situations that require ethical decisions. 5. Craft Statements: Work together to craft clear and concise statements for each core value. These statements should describe what the value means to your team. 6. Feedback and Refinement: Share the draft core values with your team for feedback. Be open to refining and clarifying the statements based on their input. 7. Finalize and Communicate: Once everyone is on the same page, finalize your team's core values. Make sure they are easy to understand and remember. Communicate them to the entire team. 8. Incorporate into Daily Work: Integrate these core values into your team's daily work. Discuss how they can guide decision-making and behavior. 9. Lead by Example: As a leader, embody these core values in your actions. Your behavior sets the tone for the team. 10. Regularly Revisit: Core values may evolve over time. Schedule periodic check-ins to ensure they still resonate with your team's identity and objectives. 11. Celebrate Values in Action: Recognize and celebrate when team members exemplify these core values. It reinforces their importance. 12. Address Misalignment: If conflicts arise or behavior doesn't align with your core values, address it promptly and use the values as a guide for resolution. Identifying core values is a collaborative process that requires ongoing commitment. By involving your team and consistently integrating these values into your work, you'll foster a culture that reflects your shared beliefs and principles. This can lead to better teamwork, decision-making, and overall team satisfaction.

Passionate problem solvers are easy to label as "too negative" or "having an agenda". Here's a good approach to bringing people on the journey: 1. Start with what you see and hear Describe specific behaviors, patterns, or outcomes as objectively as possible (knowing that we can never be truly objective). Be mindful of your potential biases. Are your emotions and perspective narrowing what you bring up? Avoid using loaded or triggering language. Keep it neutral and clear. 2. Invite others to share what they see and hear By starting with your own observations, you are setting an example for the rest of the team. Invite the team to share their perspectives and observations in ways that focus on understanding, rather than labeling or jumping to conclusions. In the right context, it might be better to start here. 3. Look inwards, observe, and listen Just as you describe outward behaviors, turn inward and notice how you feel about what you’re seeing and hearing. Instead of saying, “This place is a pressure cooker,” try, “I feel a lot of pressure.” Avoid jumping to conclusions or ascribing blame. Again, invite other people to do the same. 4. Spot areas to explore With observations and emotions on the table, identify areas worth examining. Avoid rushing to label them as problems or opportunities. Instead, frame them as questions or areas to look into. This keeps the tone open and focused on discovery. 5. Explore and go deeper As potential areas emerge, repeat the earlier steps: describe what you see, invite others to share, and observe how you feel. It is a recursive/iterative process—moving up and down levels of detail. 6. Look for alignment and patterns Notice where people are starting to align on what they’d like to see more—or less—of. Pay attention to areas where there’s consistent divergence—these are opportunities as well. Ask, “What might it take to narrow the divide?” 7. Frame clear opportunities Once patterns emerge, focus on turning them into clear opportunities. These are not solutions—they’re starting points for exploration. For example: “We could improve this handoff process” or “We’re not all on the same page about priorities.” Keep it actionable and forward-looking. 8. Brainstorm small experiments Use opportunities as a springboard to brainstorm simple, manageable experiments. Think of these as ways to test and learn, not perfect fixes. For example: “What if we tried a weekly check-in for this process?” Keep the ideas practical and easy to implement. 9. Stay grounded and flexible Be mindful of how the group is feeling and responding as you brainstorm. Are people rushing to solutions or becoming stuck? If so, take a step back and revisit earlier steps to re-center the group. 10. Step back. Let the group own it Once there’s momentum, step back and hand over ownership to the group. Avoid holding onto the issue as “your problem.” Trust the process you’ve built and the team’s ability to move things forward collectively.

Most leaders understand that collaboration matters. What they don’t understand is that collaboration is a discipline—a set of specific, learnable skills that teams can practice and improve. Walk into most collaborative efforts today and you’ll see the same pattern: ambitious goals, talented people, and meetings that meander. Leaders struggle to keep strategic conversations focused and productive. Team members leave uncertain about who’s responsible for what. Good ideas die in the gap between conversation and action. This isn’t because people lack commitment or intelligence. It’s because collaboration remains deeply misunderstood. Leaders treat it as an event—bring people together, align on goals, declare success—rather than what it actually is: a process that requires continuous attention and specific capabilities to guide. Our team at Purdue University spent 15 years working in real-world testbeds to identify what makes collaboration actually work. The breakthrough came from recognizing that productive collaborations emerge from strategic conversations built on simple rules. Each rule implies a skill that teams can learn and practice together. These are collective skills, not individual competencies. They depend on distributed leadership—team members sharing responsibility for keeping conversations productive and moving work forward. Teams strengthen these capabilities through deliberate practice, the same way musicians or athletes improve. They establish repeated habits, supported by coaching that helps groups maintain discipline long enough for new patterns to take hold. They deliberately bring together diverse ways of thinking because multiple perspectives are essential for understanding and responding to complex challenges. The payoff is substantial and immediate: less time wasted in unproductive meetings, clear accountability for action, and a disciplined process for learning and adapting as conditions change.

Organizing Teams in the Real World Organizing dev teams isn’t just about dividing headcount by the optimal Scrum team size. It’s about creating structures and interactions that minimize inefficiencies and maximize throughput. Imagine you’ve got 40 engineers (front-end, back-end, security, DevOps, BAs, etc.). Some are seasoned; others are less experienced. With limited specialists, equal skill distribution isn’t possible. So how do you balance customer focus, reduce handoffs, and optimize delivery? Approach 1: Functional Teams w/ Centralized Specialists Functional teams are organized by skill. F/E devs in one team. B/E in another. Centralized specialists support everyone. Ex: Five functional teams and a central pool of 3 security engineers and 2 DevOps experts. Pros: Deep expertise within domains. Efficient use of scarce specialists. Cons: Lots of handoffs and delays as features move between teams. Specialists become bottlenecks. Low throughput due to coordination overhead. Result: Prioritizes expertise but sacrifices efficiency and speed. Approach 2: Component Teams w/ Platform Support Component teams own specific architectural layers (e.g., database, APIs), supported by a platform team that builds reusable tools. Ex: Four component teams and a 5-person platform team for shared services. Pros: Clear ownership of systems. Standardized tools reduce redundant work. Cons: Features spanning components require coordination. Platform dependencies can delay delivery. Teams may lose focus on customer outcomes. Result: Improved scalability, but handoffs and misaligned priorities persist. Approach 3: Hybrid Cross-Functional Teams w/ Specialist Support Feature teams are organized around end-to-end business domains, supported by floating specialists or a platform team for niche needs. Ex: Six cross-functional teams, 3 floating specialists, and a 2-person platform team. Pros: Low handoffs. Teams handle most work independently. Customer-centric focus. Efficient specialist use through targeted support. Cons: Demand spikes can stretch specialists. Upskilling generalists requires investment. Result: Balances autonomy, specialization, and throughput. Best Fit: Hybrid The hybrid cross-functional model provides the best balance of autonomy, scalability, and efficiency. This topology reduces handoffs and mitigates skill shortages. Implementing the Hybrid Model 1) Organize teams around business domains (e.g., onboarding, reporting). 2) Use floating experts or a platform team for shared needs (e.g. security, DevOps). 3) Upskill generalists to reduce dependence on specialists for routine tasks. 4) Standardize tools and create reusable solutions to streamline dependencies. Reality Perfectly balanced teams are a rarity. The hybrid model delivers a practical compromise. By minimizing handoffs, focusing on customer outcomes, and optimizing the use of specialists, you can enjoy faster delivery and greater agility despite real-world constraints.