6 Integrated Leadership Practice

Set purpose and clarify the plan

Effective leadership brings people together around a shared goal, clarifies responsibilities, and helps a team adapt when priorities or circumstances change. Leadership is not limited to formal managers: any team member can take the lead when their knowledge or role best fits the situation.

A Shared purpose gives the team a concrete outcome to pursue and a reason it matters. Translate that purpose into specific tasks, owners, timelines, and decision points. Check that the plan fits available skills and resources, and invite team members to identify risks before work begins.

A useful plan answers four questions:

• What concrete, shared outcome are we trying to achieve?

• Who owns each task?

• What dependencies, constraints, or risks could get in the way?

• What practical measures and review schedule will show whether the team is on track?

When circumstances change, update the plan and communicate what changed and who is affected. This helps the team coordinate work and maintain shared understanding.

Engage stakeholders deliberately

Stakeholders are people or groups who can influence the work, are affected by it, or have information the team needs. Engagement involves more than announcing a decision: it means understanding concerns, explaining trade-offs, and providing meaningful opportunities to contribute.

A deliberate engagement process can:

1. Identify affected groups, such as customers, frontline staff, partner teams, managers, and decision-makers.

2. Ask each group about its priorities, concerns, constraints, and likely effects of the proposed work.

3. Match the message and method to the audience. An executive may benefit from a short decision brief, while staff carrying out a change may benefit more from a working session.

4. Close the Feedback loop by explaining what input changed, what did not change, and why. Share progress and invite further feedback where appropriate.

For example, before changing a customer-support process, a team lead could ask support staff to identify recurring problems, consult the team responsible for the software, and ask customers how the proposed change might affect them. A communication plan can specify the purpose, audience, message, timing, channel, and person responsible for each update.

Communicate for shared understanding

Clear communication is purposeful, specific, and two-way. Explain expectations in concrete terms, listen without interrupting, invite questions, and check what others understood. When handing off work, name the task, owner, deadline, and any conditions that require escalation. Ask the recipient to confirm the next step rather than assuming the message was understood.

For example, instead of asking someone to handle a client issue soon, specify who should contact the client, by what time, what information to confirm, where to post the outcome, and what to do if the files cannot be recovered. In the material's example, Jordan is asked to contact the client by 2 p.m., confirm which files are missing, post the outcome in the project channel, and alert the team lead before promising a new delivery date if the files cannot be recovered.

Regular check-ins help keep a team aligned. A short planning discussion can establish goals and roles, an ad hoc huddle can respond to a new obstacle, and a brief review after a milestone can capture what worked and what to improve.

Resolve conflict constructively

Conflict may arise from different priorities, incomplete information, unclear roles, or competing approaches. Address it early, focus on the work and its effects, and separate observable facts from assumptions about another person's motives. Hear each perspective, identify the shared goal, and agree on a next step.

DESC provides a practical structure for raising a concern:

• Describe the specific behavior or situation without exaggeration.

• Express its effect or why it is a concern.

• Suggest a workable alternative.

• Consequences: explain the likely benefit of the change or the risk if the issue continues.

For example, a team might explain that design requirements arrived after two review meetings, leaving little time to assess their impact and creating a risk of rework. It could suggest sending requirements a day in advance and reserving ten minutes for questions so both teams can make decisions with the same information. DESC works best when delivered respectfully and followed by genuine listening.

If a matter remains unresolved or involves serious misconduct, safety, or policy concerns, use the appropriate organizational process or seek a neutral facilitator.

Support team performance

Team performance depends on both results and working practices. High-performing teams benefit from shared goals, trust, clear communication, information-sharing, and opportunities to reflect on how they work. Leaders support these conditions by inviting questions, encouraging people to raise concerns, offering specific and timely feedback, and recognizing contributions.

Results to review might include delivery time, quality, customer feedback, or unresolved requests. Working practices to review might include whether responsibilities were clear, information reached the right people, workload was manageable, and team members could raise concerns. Use the evidence to decide what to continue, change, or investigate; do not assign blame without understanding the causes.

Integrate leadership in a project

A project team is preparing a software update for a fixed launch date. Support staff warn that the new process may confuse customers, developers say a late change could delay testing, and the project manager has not clarified who approves changes.

The team lead can:

1. Restate the shared goal: launch a tested update that customers and staff can use successfully.

2. Ask each group for its evidence, constraints, and main risks.

3. Clarify who recommends, reviews, and approves changes, and by when.

4. Agree on a brief test with support staff and a clear route for reporting problems.

5. Summarize decisions, owners, and dates in writing, then check progress at an agreed time.

6. If disagreement persists, use a respectful DESC conversation to address the specific issue and agree on a next step.

7. After the test, review customer impact, defects, timing, and team coordination, then adjust the plan.

This approach combines engagement, communication, clear leadership, and conflict resolution. It does not require every stakeholder to agree on every detail; relevant concerns must be heard, decisions explained, and responsibilities understood.