![]() ![]() That can mean different tools, separate workflows, and radically varied leadership structures from one team to the other. The great divide between teamsĮach team works their way. You could use emails and other types of asynchronous communication to try and keep everyone informed, but someone’s bound to call a meeting eventually. Collaborators and stakeholders need to be kept in the loop in real-time. The last thing you want is for one team to forge ahead with outdated information. When projects span multiple teams, keeping the lines of communication open is crucial. Kickoff meetings, weekly update meetings, emergency blocker meetings - the list goes on. ![]() Involve multiple teams and “hiccups” can quickly become “blockers.” Endless meetings Common friction points of the cross-functional project workflowĪll projects run into hiccups along the way. If you take the time to map that out, you’ll likely realize there are specific points in your workflow that don’t go as smoothly as others. This includes kickoff meetings, Slack messages, progress reports, even the creation of individual tasks in your project management tool. What do we mean by a cross-functional project workflow? It’s a workflow that encompasses everything that needs to happen before the project is declared done.
0 Comments
Leave a Reply. |