Teams Provide Resources or Workflows

By itself, the hierarchy of vertically interlocked management teams is a network of simple resource teams and not really a functional entity. There must be some horizontal workflows between the working units in order for the organization as a whole to achieve its purpose, which at minimum is survival in a competitive environment.

The organization’s component level (2) business model offers the overall upstream-to-downstream output directionality of work process. Workflow between teams requires that at least some teams have one or more internal process flows between roles, and delivers that outcome externally. Internally, team members have resource (typically including the team leader coordination role) and workflow roles. Externally, teams provide resources to or are workflow teams. Teams are the repository of the organization’s tactical “local knowledge” that arises from the interdependent configuration of tasks and roles.
A1 or other authorization link gives the team its overall purpose (charter, mission)
B1 or other process link represents delivery of team’s output

Strategy

Sponsor: “Here’s the outcome I want (measure) and the reason why (context)”

Tactics

“It’s up to you and the team to figure out the best way to do it”
Resource Team
Workflow Team
Team roles connected internally only by membership links; members often play key roles in other teams Team roles connected internally by one or more workflow links in addition to membership links
END OF MAIN CONTENT