Coaching practices for Team Input Before Project
Describe almost anything you are working through and IX Coach finds the practices whose real-world fit is closest. For Team Input Before Project, these are the strongest matches in the current practice library.
Does this sound like the set of challenges you might be facing?
- We’re about to kick off something new and everyone has private hunches about what it’ll take to pull off
- My team keeps dropping the ball at the same stage every single project
- Every time an urgent little task lands on my team there’s this awkward pause where nobody’s sure whose job it is, so it either drops or whoever’s least busy gets stuck with it again
- I keep dragging the big-picture dreamers into the tedious finishing work and asking my finishers to brainstorm wild ideas, and everyone’s miserable and the handoffs are a mess
- People drop new "can you reprioritize this" requests on my team all week long and whoever asks loudest or latest wins
Practices that may help
- Use feedforward to align team members on goals before projects begin
At the start of a project, invite feedforward on how to succeed — before any performance to critique.
Feedforward: Future-Focused Feedback That Actually Changes Behavior - Map your team’s genius coverage
Check whether all six activities are covered by someone who finds them energizing.
The 6 Types of Working Genius (Patrick Lencioni) - Establish an explicit delegation protocol for Q3 tasks
Define in advance who receives which types of urgent-but-not-important tasks — before they arrive.
The Eisenhower Matrix for Teams - Assign project phases to genius-matched people
Route early ideation to Wonder/Invention geniuses and execution phases to Tenacity geniuses.
The 6 Types of Working Genius (Patrick Lencioni) - Run a single weekly priority-setting meeting
Replace ad-hoc priority requests with one weekly meeting where the whole team re-sorts together.
The Eisenhower Matrix for Teams - Adjourning: close the team with intention
How a team ends shapes how each member begins the next one.
Tuckman’s Stages of Team Development - Define "important" explicitly as a team
Before sorting tasks, align on what "important" means — which goals, for whom, over what time horizon.
The Eisenhower Matrix for Teams - Protect important-not-urgent work as a team commitment
Schedule Q2 work on a shared calendar so urgent tasks can’t claim it by default.
The Eisenhower Matrix for Teams - Brainwrite instead of group brainstorm
Have people generate ideas silently and individually first, then pool and build.
Divergent Thinking: Generating Many Ideas - Forming: provide clarity before connection
In the first stage, a new team needs structure and purpose more than it needs team-building.
Tuckman’s Stages of Team Development
Related concerns
- Atomic Habits With My Team
James Clear’s system says behavior change is a system problem, not a willpower problem: make a desired habit obvious, attractive, easy, and satisfying — and do the reverse for bad ones. The most load-bearing ideas (implementation intentions, friction reduction, identity-based change) are well supported in the research literature.
- How To Align Team Priorities
Before sorting tasks, align on what "important" means — which goals, for whom, over what time horizon.
Define "important" explicitly as a team
- Protect Important Work Team
Schedule Q2 work on a shared calendar so urgent tasks can’t claim it by default.
Protect important-not-urgent work as a team commitment
- Team Prioritization
Replace ad-hoc priority requests with one weekly meeting where the whole team re-sorts together.
Run a single weekly priority-setting meeting
- Team Prioritization Cadence
Replace ad-hoc priority requests with one weekly meeting where the whole team re-sorts together.
- Team Prioritization Exercise
Replace ad-hoc priority requests with one weekly meeting where the whole team re-sorts together.
Describe your situation in your own words to search the complete practice library.