On communication
Constant, concise communication is the engine of a high-performing team.
In a busy IT function, things move fast and priorities shift. Without a regular, structured rhythm of communication, teams drift - work gets duplicated, blockers go unspoken, and the people closest to the problems stop feeling heard. The 10Past cadence puts communication back in the hands of team leads: short, sharp, action-focused sessions that keep everyone aligned without consuming the day.
10Past principles
1
Priority Issues
Bring your main priority, roadblock, or challenge to raise in the meeting.
2
Valuable and Concise
10Past Huddles are clinical and aim to give everyone direction and awareness.
3
Metrics and Measurables
Key metrics for each team should be recorded in every session.
POP
The POP Principle
Sessions have a clear Purpose, an intended Outcome, and an agreed Process.
Week at a glance
Monday
10:10AMCross-Vertical
11:10AMInfra & Security
3:10PMDevelopment
Tuesday
10:10AMIT Operations
11:10AMInfra & Security
2:10PMServices & Support
Wednesday
11:10AMInfra & Security
2:10PMServices & Support
3:10PMDevelopment
Thursday
10:10AMIT Operations
11:10AMInfra & Security
2:10PMServices & Support
Friday
11:10AMInfra & Security
3:10PMDevelopment
Vertical huddles
2x / week
10:10AM10Past~15 mins
▼
Chair: IT Ops Lead
Change calendar, incidents, problems, project status, training pipeline.
IT Infrastructure and Security
5x / week
11:10AM10Past~15 mins
▼
Chair: Infrastructure and Security Lead
Threats, vulnerabilities, platform and Azure changes. CW IT Lead attends every session.
3x / week
2:10PM10Past~15 mins
▼
Chair: Service Desk Manager
Metrics: ticket volume, queue vs yesterday, workload spread.
Additional participants
Xerox external team lead attends as partner representative for outsourced support visibility.
3x / week
3:10PM10Past~15 mins
▼
Chair: Dev Lead
Sprint priorities, blockers, cross-vertical dependencies flagged to Infra and Ops.
Cross-vertical huddle
Monday · All chairs · 10Past
Cross-Vertical Huddle
Mon 10:10AM10Past~15 mins
▼
Attendees
MR
Michael Rammell
CW IT Lead · chairs the session
V1
Service Desk Manager
IT Services and Support
+ 1
V2
Infrastructure and Security Lead
IT Infrastructure and Security
+ 1
V3
IT Ops Lead
IT Operations
+ 1
Agenda per chair
1
Short summary of ongoing initiatives across the vertical
2
One priority issue, roadblock, challenge, or update for the group
3
Open to group input, cross-vertical support, or CW IT Lead steer
Attendance expectation: Chairs are expected to attend in person. In absence, a nominated deputy attends on their behalf. Each chair may bring one additional attendee. The CW IT Lead will attend vertical huddles according to current firm priorities and where a roadblock or escalation requires their presence.
Every session opens with a clear statement of why the team is meeting. It is stated, not assumed framing what matters for that session.
- State the reason for the meeting in one sentence
- Confirm the team is aligned on what the session is for
- Set the boundary what is in scope today
Outcome
What does good look like?
▼
Before discussion begins, the chair names what a successful session looks like keeping the team focused on a destination, not just a conversation.
- Define what done looks like for this session
- Name the decision or action that makes this a success
- Give the team a shared definition of progress
Process
How will we get there?
▼
At the close of every session, agreed next steps are named who owns what, by when. No session ends without a clear path forward.
- Confirm actions, owners, and deadlines before closing
- Record blockers that need escalation outside the session
- Leave everyone knowing exactly what happens next
IT Infrastructure and Security
Why 10Past?
The case for a branded, consistent communication cadence.
- Short, sharp and concise
- Memorable, consistent timing
- Allows previous meetings to overrun
- Allows prep time (notes, coffee, comfort break)
- Ensures all participants are ready, engaged and come away with value