Effective Tech Project Management Techniques

😮 5% of people are responsible for 35% of the valuable collaboration in your organization.   One of the highlights of my time at the Tulsa Remote Plugged In Conference was meeting Rebecca Hinds, PhD, Head of Asana's Work Innovation Lab. Onstage she gave a presentation jam-packed with great insights about what it takes for effective team collaboration. Offstage we got to share stories about how what her research shows is what I see on a daily basis as we work with cross-functional distributed and hybrid teams. And how teaching teams to create their team charters / team working agreements to codify goals, roles, and ways of working leads to more effective collaboration and more teammate connection. Key takeaways from her presentation, "5 Research-Backed Strategies to Drive Better Collaboration": 1. Collaboration equity 52% of employees say their teams rely on a few high performers to get work done. When Asana provided a dashboard to show how collaboration was distributed across the team, 93% made meaningful changes when it was visible who needed to step back and others needed to step up 2. Cross-functional collaboration The most innovative firms have 30-50% of their ties established cross-functionally. Example: for tech companies the top predictor of innovation is strength of collaboration between marketing and engineering 3. Collaboration across physical space Asana research shows that the current behavior is for people to do more cross functional collaboration on in-office workdays than on remote workdays. [My 2 cents → this is why building what I call "Omni-modal" leadership skills is so critical, so that people are equally skilled at collaborating in a remote or hybrid setting as they are in an in-person setting. Especially since many people need to switch between these modes even within the same day. ] 4. Collaboration across work The connection between tasks and goals is a massive driver of employee engagement. Only 55% of workers in remote and hybrid orgs are clear on how their work helps their company reach its goal. For every 10 pieces of work related to goals there is + 7% increase in engagement. For every 100 pieces there is a +101% increase in engagement. 5. Collaboration with AI Treat it like a teammate, not just a tool. When used daily, 89% of people say they get productivity gains. But AI needs cross-functional context to enable the best collaboration. P.S. a big thanks to Justin Harlan and Betsy Slagle for pulling together a well-crafted event with a great line-up of speakers! #tulsaremote #virtualleadership #hybridteams

Over the years, I've discovered the truth: Game-changing products won't succeed unless they have a unified vision across sales, marketing, and product teams. When these key functions pull in different directions, it's a death knell for go-to-market execution. Without alignment on positioning and buyer messaging, we fail to communicate value and create disjointed experiences. So, how do I foster collaboration across these functions? 1) Set shared goals and incentivize unity towards that North Star metric, be it revenue, activations, or retention. 2) Encourage team members to work closely together, building empathy rather than skepticism of other groups' intentions and contributions. 3) Regularly conduct cross-functional roadmapping sessions to cascade priorities across departments and highlight dependencies. 4) Create an environment where teams can constructively debate assumptions and strategies without politics or blame. 5) Provide clarity for sales on target personas and value propositions to equip them for deal conversations. 6) Involve all functions early in establishing positioning and messaging frameworks. Co-create when possible. By rallying together around customers’ needs, we block and tackle as one team towards product-market fit. The magic truly happens when teams unite towards a shared mission to delight users!

The successful adoption of legal technology requires a methodical approach that balances innovation with practical implementation. Key elements include: 1) Strategic Process Mapping Understanding your current workflow forms the foundation of effective digital transformation. Begin by documenting how your team actually works—not how they should work on paper. This means tracking time allocation across tasks, identifying repetitive processes, and gathering direct feedback from clients about service delivery pain points. By mapping these workflows to strategic objectives, firms can identify where technology can create the most significant impact. 2) Outcome-Based Goal Setting Move beyond abstract objectives by establishing concrete, measurable targets that link directly to business outcomes. Rather than pursuing technology adoption for its own sake, focus on specific improvements in service delivery. For example, reducing contract review time from four hours to one hour per document provides a clear metric for success. 3) Rigorous Solution Evaluation Have your team (and likely key users) test potential solutions using their most challenging matters and complex workflows. Further test solutions through sandboxes and proof of concept excercises. This practical evaluation approach helps ensure that selected tools address real needs rather than creating additional complexity. 4) Structured Implementation Planning Successful technology adoption requires dedicated leadership and clear accountability. Develop a phased rollout plan that designates practice group champions and establishes regular review cycles. These champions should have allocated time for implementation oversight, and the firm should conduct formal assessments at 30, 60, and 90-day intervals to measure adoption progress and address emerging challenges. Note: I've already shared in a prior post another critical element - change management. The link to it is in the comments. #legaltech #innovation #law #business #learning

"Siloed development” has come up again and again in our latest research. It’s a quiet killer of innovation, especially in hybrid organizations. Right now, teams solve the same problems in parallel. This can manifest itself in a variety of ways, from data being trapped in departments to AI tools being used to amplify isolation instead of alignment. That’s why today, in an age where AI is being used to accelerate every function in the workplace, the organizations that connect rather than compartmentalize will be the ones that succeed. In order to do that, Teamship needs to be brought in. In Never Lead Alone, I define Teamship as cross-functional collaboration without hierarchy. In other terms, this means trust is more important than titles and peers co-elevate one another toward a shared mission. Teamship the foundation of a new AI + Human Leadership Playbook, one built on: 1. Peer-to-peer accountability: Teams hold each other responsible for outcomes and deliverables. 2. Co-created intelligence: AI helps surface insights across functions and humans connect the dots. 3. Architected hybrid patterns: Intentional design of when and how teams intersect, so collaboration becomes more of a habit. Breaking silos is a behavioral and relational challenge as much as it is a structural one. And it starts with leaders who replace “my team” with “our team.”

𝗛𝗼𝘄 𝘁𝗼 𝗕𝗿𝗲𝗮𝗸 𝗗𝗼𝘄𝗻 𝗦𝗶𝗹𝗼𝘀 𝗶𝗻 𝗠𝗲𝗱𝗧𝗲𝗰𝗵 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁: (𝗖𝗿𝗲𝗮𝘁𝗶𝗻𝗴 𝗰𝗿𝗼𝘀𝘀-𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝗵𝗮𝗿𝗺𝗼𝗻𝘆 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝘁𝗵𝗲 𝗵𝗲𝗮𝗱𝗮𝗰𝗵𝗲𝘀) 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

A common partnership snafu is that companies want partnership success, but don’t provide the resources to get there. I heard of a case where a whole marketing team quit, the partnerships team was given no marketing support, and they didn't yet have an integration with product -- and yet, the CEO expected the partnership strategy to deliver instant revenue. Wild. But not uncommon. Partnerships can't thrive in a vacuum. They need cross-functional support—marketing, product integration, sales enablement—all aligned to succeed. Before you set revenue targets for your partnerships, ask yourself: Do we have the resources to support them? If the answer is no, you have to help your leadership teams to reconsider their expectations. To help create the cross-functional support needed for partnerships to thrive, here are four strategies: 1. Involve Cross-Functional Leaders from the Very Beginning Bring key leaders from marketing, sales, and product into the partnership planning phase. Early involvement gives them a sense of ownership and ensures they understand how partnerships align with their own goals. Strategy: Schedule a kick-off meeting with stakeholders from each relevant department. Create a shared roadmap that outlines how partnerships will impact each team and their specific contributions. 2. Tie Partnership Success to Department KPIs To gain buy-in, tie partnership goals directly to the KPIs of each department. Aligning partnership outcomes with what each team is measured on ensures they have skin in the game. Strategy: During planning sessions, ask each department head how partnerships can contribute to their targets. Build specific KPIs for each function into the overall partnership strategy. 3. Create a Resource Exchange Agreement Formalize the support needed from each department with a resource exchange agreement. This sets clear expectations on what each function will contribute—whether it's a dedicated product team member for integrations or marketing resources for co-branded campaigns. It turns vague promises into commitments. Strategy: Draft a simple document that outlines the roles, responsibilities, and deliverables each team will provide, then get sign-off from department heads and the executive team. 4. Demonstrate Early Wins for Buy-In Quick wins go a long way toward securing ongoing resources. Identify a small pilot project with an internal team that shows immediate impact. Whether it's a small co-marketing campaign or a limited integration, these early successes build momentum and demonstrate the value of supporting partnerships. Strategy: Select one or two partners to run a pilot with, focused on delivering measurable outcomes like leads generated or product adoption. Use this success story to demonstrate value to other departments and secure further commitment. Partnership success requires cross-functional alignment. Because partnerships don’t happen in a silo.

In so many organisations, so many people have so many ideas, skills and knowledge sets that could be of incredible value but their voices so often go unheard, because they work in a team or department that isn’t leading on the challenge, or their job description is only accessing 10% of their experience, expertise and interest. It is why it is so important to get people to work across teams and to broker and to catalyse that. The U.S. military have liaison officers who facilitate communication between elements of the organisation to ensure mutual understanding and unity of purpose and action. Liaison is the most commonly employed technique for establishing and maintaining close, continuous, physical communication between commands. It ensures that leaders and teams have a real time awareness of talent and expertise, wherever it may be, so that it can be deployed quickly and with immediate impact. Maybe, create a centralised information centre, where people can see what is going on where in the organisation, and can contribute through online portals to offer support and ideas. Increasingly, organisations are holding hackathons, during working hours for people to meet in open spaces, shares ideas and challenges, in order to form working groups and focused teams. I often advise clients to build work exchanges into their professional development cycles, so that people get the chance to experience other roles and responsibilities within the organisation, not only to build empathy but to foster new relationships and opportunities for information and idea exchanges. Start to see roles as missions rather than fixed job descriptions, so that colleagues can move when appropriate but always have a home base to return to.   Make sure that leaders at all levels are not only held to account for planning, strategy, vision, culture and performance but for cross-team collaboration. It is too easy for leaders to role model the silo-ing and cross departmental blame shifting that can so easily poison an organisation’s collegiate potential.  

A few weeks ago, I sat down with a friend who runs a mid-sized software agency. He’d just wrapped up a fixed-price project for a client. At first, everything seemed perfect: - The contract was neat. - The price was set. - The scope was clear. But halfway through, cracks began to show. The client wanted new features. “Just a small addition,” they said. Then another. Before long, the project scope looked nothing like the original plan. But the price? That stayed the same. My friend tried to manage the changes, but his hands were tied. The fixed-price contract didn’t allow flexibility. So, he had two choices: 1. Absorb the extra work and take the financial hit. 2. Push back and risk souring the client relationship. Both options were painful. By the end of it, he’d burned time, money, and trust—without turning a profit. On paper, fixed pricing sounds perfect: • Predictable costs • Simplicity • A sense of control But here’s the truth: Tech projects are rarely predictable. Scope changes, new requirements, and unexpected challenges are inevitable. A fixed-price contract locks in your costs—but it also locks in your flexibility. When the project evolves (and it will evolve), you’re left with three bad options: • Cut corners • Absorb costs • Fight over what’s “in scope” That’s not control. That’s chaos. Now the best contracts don’t eliminate risks—they anticipate change and build processes to handle it. Here’s how: 1. Define a Clear Change Order Process • Outline how changes to the scope will be handled. • Include timelines, approval steps, and cost adjustments. 2. Negotiate Flexibility from the Start • Be upfront about the potential for scope changes. • Build in buffer time, additional fees, or flexible milestones. 3. Shift the Mindset Around Fixed Pricing • Treat it as a starting point, not a cage. • Fixed pricing should provide stability—not kill adaptability. Now let’s rewind to my friend’s situation—but this time, he has a solid change order process. When the client requests a new feature, he refers to the contract: “We can absolutely add this feature. Let’s create a change order to adjust the timeline and budget.” • The client understands the process because it was outlined from day one. • The project adapts smoothly. • And my friend? He gets paid for the extra work. Now fixed pricing isn’t a bad idea, but it’s not risk-free. A great contract balances cost stability with room for adjustments. By planning for change upfront, you protect your business from surprises—while keeping your clients happy. In the unpredictable world of tech projects, flexibility isn’t optional. It’s necessary. —— 📌 If you need my help with drafting custom contracts for your high-ticket projects, then DM me "Contract". #Startups #Founders #Contract #Law #Business

In transformation, how do you solve the conflict between a function owner having accountability just for their function and an end-to-end accountable owner having authority across functions? I’ve been giving this some thought. I believe we need to separate accountability for capability (functional owners) from accountability for outcomes (end-to-end owner), and then hard-wire how conflicts are resolved. 💡 Functional owners retain authority over standards, people, and domain execution. They control: 👉 How work is done within their function 👉 Technical standards, controls, and compliance within their domain 👉 Resource allocation inside their team They are accountable for quality of input, not the end business outcome. 💡 The end-to-end owner has decision rights over prioritisation and trade-offs. They control: 👉 Sequencing of work across functions 👉 Allocation of shared capacity where conflicts arise 👉 Acceptance criteria for what “good” looks like across the full flow 👉 Trade-offs between speed, cost, and risk at the system level They are accountable for outcome delivery, but they do not manage the functional teams day-to-day. 💡 A formal “tie-break” mechanism should be defined upfront. When there is a conflict: 👉 It escalates to a clearly defined forum (not ad hoc discussion) 👉The end-to-end owner has the final decision within agreed guardrails 👉 Functional owners retain veto only where regulatory/compliance thresholds are breached 💡 Incentives are aligned to shared outcomes, not just functional KPIs. 👉 If a function is only measured on local efficiency, it will rationally resist cross-functional trade-offs 👉 A portion of performance measurement needs to reflect contribution to the end-to-end outcome 💡 Constraints are made explicit, not negotiated repeatedly. 👉 Functions publish their non-negotiables (regulatory limits, capacity ceilings, architectural constraints) 👉 The end-to-end owner plans within those constraints rather than rediscovering them during delivery ✅ The underlying principle is: 👉 Functional owners control how, end-to-end owners control what and when, and governance defines who decides when they disagree What are my networks thoughts on this?

How to Write a Project Plan Creating a project plan is essential for ensuring the successful execution of any project. A well-crafted project plan is a roadmap, detailing the steps necessary to complete the project within scope, on time, and within budget. 1. Define the Project Scope Start by clearly defining the project’s scope. This involves outlining the project’s goals, deliverables, and boundaries. A well-defined scope helps prevent scope creep and keeps the team focused on the primary objectives. 2. Identify Stakeholders List all stakeholders involved in the project, including the project sponsor, team members, clients, and other relevant parties. Understanding who has a vested interest in the project’s outcome helps in aligning goals and expectations. 3. Establish Objectives and Deliverables Break down the project into specific, measurable objectives. Each objective should contribute to the overall goal of the project. 4. Develop a Work Breakdown Structure (WBS) Create a Work Breakdown Structure to organize the project into manageable sections. The WBS breaks down the project into smaller components, tasks, and subtasks. This hierarchical structure makes it easier to assign responsibilities, estimate costs, and manage timelines. 5. Create a Schedule Develop a detailed project schedule using the WBS. Identify the start and end dates for each task, and sequence them logically. Use tools like Gantt charts to visualize the timeline and dependencies between tasks. 6. Assign Resources Allocate the necessary resources for each task, including team members, equipment, and materials. Clearly define roles and responsibilities to ensure everyone knows what is expected of them. Consider team members’ availability and skill sets to make the most effective use of your resources. 7. Develop a Budget Estimate the costs associated with the project, including labor, materials, and overheads. Develop a budget that aligns with the project scope and objectives. Ensure to include contingencies for unexpected expenses. 8. Identify Risks and Mitigation Strategies Conduct a risk assessment to identify potential challenges that could impact the project. Document these risks and develop mitigation strategies to address them. 9. Plan for Communication Develop a communication plan to ensure effective information flow among stakeholders. Specify how and when updates will be provided, the communication channels to be used, and the type of information to be shared. 10. Monitor and Control Implement a system for monitoring and controlling the project’s progress. Use performance indicators to track progress against the plan. Regularly review the project plan and make adjustments as necessary to address any deviations. Image Source: Template22.Com #projectmanagement #projectmanagementtools #management #managers #engineers #successfulprojectmanagers #construction #civilengineering #civil