Profile of the ideal manager to develop collaborative work

Why collaborative work calls for a new kind of manager

Collaborative work is no longer just about sharing a folder on a common server or holding more team meetings. In a few years, organizations have moved to hybrid, cross-functional and distributed ways of working that profoundly redefine the manager's role. Where hierarchical authority used to be enough to coordinate, managers now have to lead, align and arbitrate in real time, often without being physically present.

Teams spend a large share of their time on collaborative activities: emails, meetings, instant messaging. Yet those exchanges do not always produce clear, traceable decisions. The problem is not the amount of interaction, it is the lack of structured steering behind it.

Three shifts that are changing operational management

The evolution of collaborative work over the past 30 years shows three major shifts that management now has to answer:

• Cross-functionality. Projects bring together multidisciplinary teams with no direct reporting line. The manager becomes a facilitator across functions, not just the head of a silo.
• Distance. Remote work and multi-site teams require steering at a distance. Without a structuring tool, visibility on progress collapses and emails multiply to compensate.
• Pace. A monthly dashboard is no longer enough. Operational excellence approaches call for living indicators and adjustments in short loops, following the PDCA logic (Plan, Do, Check, Act).

The new key skills of the collaborative manager

Faced with these shifts, the managerial profile is changing in concrete ways. A manager in an industrial company who used to lead a team in a workshop may now have to coordinate quality leads, IT project managers and field teams spread across several sites, sometimes without direct authority over half of them. It is no longer just management, it is running a network.

The skills now expected combine methodological rigor and relational intelligence:

• Clarifying roles. Tools such as the RACI matrix remove grey areas on who decides, who carries out and who approves. Without that clarity, collaborative work creates duplication and tension rather than performance.
• Steering by results. Rather than checking presence or hours, the collaborative manager follows shared indicators and dashboards that the whole team can read.
• Structuring rituals. Short, decision-oriented steering meetings replace time-consuming informal check-ins. Every exchange produces actionable minutes, not a list of good intentions.
• Encouraging autonomy without losing consistency. Collaborative management is not laissez-faire. It requires a clear framework (objectives, deadlines, owners) within which everyone has real room to maneuver.

The manager who succeeds in a collaborative environment is not the one with the most authority, but the one who creates the best conditions for the team to make good decisions quickly.

Visionary: giving meaning to align teams

An organization is not steered only with tools; it is steered with a shared vision. When every employee understands why they are acting, alignment becomes natural: priorities become clearer, trade-offs simpler and collective performance faster.

Without an explicit vision, teams work in silos: each department optimizes its own scope without overall consistency. Meetings multiply to recalibrate, emails pile up to make up for the lack of a common direction, and action plans struggle to converge. Vision is not a managerial luxury: it is the invisible infrastructure of operational excellence.

From vision to indicators: a structured cascade

Moving from vision to measurable results follows a cascade that runs both downward and upward, on three levels:

1. Strategic vision: the three to five year ambition, carried by management.
2. Tactical objectives (OKRs and KPIs): broken down by department or business unit, with measurable result indicators over the year.
3. Operational action plans: each team knows what it must do, by when and with which milestones. Collaborative work becomes the lever of execution, not an option.

This cascade fits naturally with the PDCA method described in our continuous improvement guide. Each cycle checks that the actions under way remain aligned with the strategic objectives, and adjusts course if the gap widens.

Concrete examples of alignment through vision

In manufacturing, an operations director sets a target for machine availability. Each maintenance team sees its own actions linked to that objective, and immediately understands the impact of its delays on overall performance. In a franchise network, the central vision (for example, customer satisfaction) is broken down into site-by-site action plans, followed from a consolidated dashboard. For executive committees, the vision becomes the common thread of every steering meeting: progress updates stop being activity reports and become measures of strategic alignment.

Leader and communicator: two sides of the same posture

People often contrast the operational manager, focused on results, indicators and deadlines, with the inspiring leader, concerned with meaning and motivation. That opposition is a trap. In collaborative work, leadership and communication are not two separate skills used in turn: they form a single posture, exercised continuously.

Take a concrete example. A quality manager runs a continuous improvement cycle with the PDCA method. They master the Plan, Do, Check, Act steps, can read their quality indicators and can spot a drift. But if the team does not understand why each action is a priority, and if decisions stay in the manager's head instead of being shared in a common space, the cycle seizes up. Performance does not depend on the method alone: it depends on the manager's ability to circulate meaning as much as information.

Why communication is an act of leadership

A leader who does not communicate clearly produces three predictable effects: more reminder emails (a sign of missing shared visibility), the gradual demotivation of people who cannot see the impact of their work, and fragmented efforts, with everyone pulling in a different direction for lack of a readable course.

Communicating as a leader does not mean holding more meetings or writing exhaustive memos. It means choosing the right moment, the right channel and the right level of detail. It means turning a decision into a shared conviction. It also means holding back what has not yet been decided, to avoid noise, and amplifying what is moving forward, to keep momentum. In a Kaizen or operational excellence approach, every small improvement is worth making visible: it feeds collective motivation well beyond its intrinsic value.

Distributed leadership: when every member becomes a relay

The model of a single leader-communicator has had its day. In organizations with a high level of collaborative maturity, leadership is distributed: every action owner and every process lead becomes a communication node in turn. This ties in directly with clarifying roles: knowing who decides, who is informed and who acts also defines who communicates what to whom.

A manager who structures action plans with clearly designated owners, visible due dates and shared progress statuses, without having to chase people by hand, leads through structure as much as through words. The tool becomes an extension of the posture: it makes communication systematic without making it heavy.

Signs of a mismatch between posture and communication

• Teams discover priorities in meetings instead of seeing them coming in a shared space.
• Motivation drops after each performance review, for lack of a clear story about the progress made.
• Alerts do not travel up: the manager is the last to know about blockers.
• Emails multiply to make up for the lack of shared visibility.

These signs are not people problems, they are system problems. A manager can be technically excellent and a brilliant speaker and still produce these dysfunctions if their communication is not supported by tools and rituals.

Flexible and factual: deciding in an uncertain environment

When priorities change every week, operational excellence no longer rests on rigid plans. It rests on the ability to decide quickly, based on facts, and to adjust course without losing the thread. Flexibility without data is improvisation. Data without flexibility is paralysis. The balance between the two is what distinguishes high-performing teams.

The PDCA cycle, the foundation of quality management and Kaizen, offers exactly this framework: iterate in short cycles, measure the gap between planned and actual, and correct before the gap becomes a drift. Without a suitable tool, though, the cycle remains theoretical.

Fact-based decisions vs gut feeling: what a well-tracked indicator changes

An indicator is only worth something if it triggers an action. Too often, indicators sleep in Excel files opened once a month. When each indicator is linked to an owner, a due date and a corrective action plan, measurement becomes a real steering lever. In an industrial setting, for example, a non-conformity rate that crosses a threshold leads to a QHSE action plan, assigned to the right person and visible to all, with no need for a reminder email or a meeting to notice the problem.

Dimension	Without a structured tool	With a steering tool
Indicator tracking	Scattered Excel files, updated by hand	Centralized indicators, updated continuously
Decision-making	Based on intuition or outdated data	Factual, anchored in measured gaps
Improvement cycle	Theoretical PDCA, without tools	PDCA built into daily steering
Flexibility	Responsiveness slowed down by email exchanges	Actions reassigned quickly, built-in alerts
Traceability	History lost between emails and meetings	Full history of actions and decisions

Agility does not mean a lack of rigor

Operational flexibility is often misunderstood: it does not mean changing course for no reason, but adapting action plans to the real signals the indicators send back. In a Kaizen approach, every small gap is an opportunity for improvement, provided it is detected early enough. A fact-based decision is also only valuable if it is shared quickly: clear channels, not endless email threads, are what effective collaborative work relies on.

The tools that extend the collaborative manager

Adopting a collaborative management posture is not enough: you also need an operational environment that turns the intention into concrete habits. The table below matches the essential managerial skills with the levers a steering tool such as Perfony provides.

Key skill	Concrete operational challenge	What Perfony provides
Clarifying responsibilities	Who does what? Who decides? Grey areas create duplication and blockers.	Each action assigned to a named owner, RACI roles in the plans, automatic alerts to the owner
Steering by objectives (KPIs, OKRs)	Following progress without time-consuming status meetings or scattered Excel files	Dashboards and KPIs that show gaps and link them to corrective actions
Running effective meetings	Decisions made in meetings get lost for lack of structured minutes and follow-up	AI-assisted meeting minutes, decisions turned into actions, reminders to participants
Reducing information overload	Reminder emails and status chains saturate inboxes and bury what matters	Targeted notifications and a central collaborative space for action follow-up
Building continuous improvement into the team	A PDCA or Kaizen approach without a dedicated tool stays superficial and untraceable	Plan, Do, Check, Act structure, history of cycles, link with quality indicators
Keeping multi-site consistency	Aligning geographically dispersed teams on the same operational priorities	Consolidated views across entities, shared action plans, AI summaries of progress by site

What these examples show is that the tool does not replace the manager, it amplifies their posture. A manager who already practices structured delegation, active listening or quality management will see those behaviors multiplied by a consistent digital environment. Without a supporting framework, even the best managerial intentions run into everyday friction: cascading emails, meetings with no follow-up, forgotten actions.

To measure the real impact of these practices, read our article on measuring the effectiveness of collaborative work.

In practiceGive your collaborative management the right toolsEvery action has an owner, a due date and a status that everyone can see. Fewer status meetings, fewer reminder emails. Integrated with Teams and Outlook, hosted in France.Discover the action plan software