Coaching practices for Activities for Different Companies in One Workplace
Describe almost anything you are working through and IX Coach finds the practices whose real-world fit is closest. For Activities for Different Companies in One Workplace, these are the strongest matches in the current practice library.
Does this sound like the set of challenges you might be facing?
- Every project I’m juggling lives in one giant shared list, so when I sit down to focus on one thing I have to mentally sift past everything else first, and I can never tell how far along any single project actually is.
- My days are a blender
- My whole week is an undifferentiated blur where every single day mixes a bit of everything, and I end most of them drained and somehow with nothing finished
- My whole week funnels me past the exact same faces
- All our communication is ad-hoc
Practices that may help
- Keep each project’s Action Steps physically separate from other projects
Mixing action steps from different projects in a single list increases context-switching cost and makes progress harder to see.
The Action Method, Made Practical - Assign broad themes to days of the week
Dedicate each weekday to a broad category of work (deep creation, meetings, admin) to reduce context-switching.
Ideal Week Design - Assign a theme to each day of the week
Decide in advance which type of work each weekday is for and protect those assignments.
Theme Days, Made Practical - Design for serendipitous encounters
Put yourself in environments where unexpected, cross-cluster contact is structurally likely.
The Strength of Weak Ties - Establish a full meeting rhythm from daily to annual
Align daily, weekly, monthly, quarterly, and annual meetings into a coherent cadence that replaces ad-hoc communication.
The Rockefeller Habits: Scaling Up with Rhythm and Focus - Let the report own the agenda
It’s their meeting — they bring what matters to them, and you adapt to it.
Effective One-on-Ones, Made Practical - Batch all meetings onto meeting days
Route all collaboration, calls, and meetings into dedicated days so they don’t fragment the rest.
Theme Days, Made Practical - Run a regular team elimination review
Periodically review what the team is doing that no longer serves any current goal.
The Eisenhower Matrix for Teams - Dedicate a day (or half-day) to administrative work
Process email, admin, and low-cognitive tasks in a bounded time so they don’t leak into high-value days.
Theme Days, Made Practical - Batch meetings into one or two days per week
Cluster all coordination into designated meeting days so the remaining days stay structurally intact.
Maker vs Manager Schedule
Related concerns
- Communicate Theme Days
Theme days assign a single type of work to each day of the week — for example, Mondays for meetings, Tuesdays for deep work, Wednesdays for administrative tasks — so context-switching is minimized and cognitive setup costs are paid once per day rather than many times. The approach is a practitioner structure consistent with attention-residue and task-switching research, but has not been formally trialed as a specific technique.
- Focus Day Strategy
Cluster all coordination into designated meeting days so the remaining days stay structurally intact.
Batch meetings into one or two days per week
- When Time Blocking Day Theming
Dedicate whole days to a single domain of work — writing day, meetings day, admin day.
Day theming
- Admin Theme Day
Theme days assign a single type of work to each day of the week — for example, Mondays for meetings, Tuesdays for deep work, Wednesdays for administrative tasks — so context-switching is minimized and cognitive setup costs are paid once per day rather than many times. The approach is a practitioner structure consistent with attention-residue and task-switching research, but has not been formally trialed as a specific technique.
- Batch Similar Work By Day
Dedicate whole days to a single domain of work — writing day, meetings day, admin day.
- Calendar Design Themes
Theme days assign a single type of work to each day of the week — for example, Mondays for meetings, Tuesdays for deep work, Wednesdays for administrative tasks — so context-switching is minimized and cognitive setup costs are paid once per day rather than many times. The approach is a practitioner structure consistent with attention-residue and task-switching research, but has not been formally trialed as a specific technique.
Describe your situation in your own words to search the complete practice library.