LOFIDAWN
Systems Engineering · Team Lead
Work Dashboard
Today's Focus
Send /work plan to generate today's focus
No must-dos set. Drop tasks into the bot and say /work plan.
Active Projects
No projects yet
Send:
I'll generate a full brief, ADR, workflow, and runbook.
/work project [description]I'll generate a full brief, ADR, workflow, and runbook.
KTLO / Oncall
No KTLO items
Send:
I'll track frequency and flag when overdue.
/work add [recurring task]I'll track frequency and flag when overdue.
Commands
/workCurrent focus + what to work on next
/work project [desc]Full brief + ADR + workflow + runbook
/work add [task]Add task or KTLO item (auto-categorised)
/work planToday's time-blocked focus plan
/work weekWeekly review + next week priorities
/work done [task]Mark complete
/work adr [decision]Architecture Decision Record
/work delegate [task]Delegation plan with owner + follow-up
Delegation Framework
Your time = final decisions + irreducible context. Everything else is delegated or bot-owned.
| Task | You own | Delegate / Bot owns |
|---|---|---|
| Architecture decisions | Final call | ADR draft, options analysis, trade-offs |
| Code review | Complex / risky PRs | Routine PRs → senior ICs; bot does first-pass |
| Team unblocking | Context + judgment | Research, draft answers, dig into logs |
| Incident response | Command decisions | Runbook, log analysis, postmortem draft |
| Stakeholder updates | Review + send | Draft from project state |
| Meeting prep | Attend + lead | Agenda, briefing notes, follow-up actions |
| Tech research | Evaluate + decide | Deep dive, compare options, summarise |
| Documentation | Review accuracy | Write it — RFCs, runbooks, ADRs, postmortems |
| KTLO / Oncall | Escalation decisions | Automate, write runbooks, triage alerts |
Delegation Tips
- 1Delegate outcomes, not tasks. "Make deploys reliable" not "fix step 3 of the pipeline". Let them own the how.
- 2Set autonomy level upfront. "Do it and tell me after" vs "check with me before sending". Ambiguity creates unwanted check-ins.
- 3Follow up at agreed checkpoints, not randomly. Random check-ins = micromanagement. "Sync me Thursday." Then leave them alone.
- 4If you're the bottleneck, that's a system problem. PRs waiting on you, decisions waiting on you — redesign the system, not your calendar.
- 5Never take back a delegated task. Coach them through it. Taking it back trains them to escalate every time.
- 6Protect 9–11 AM deep work. If you can be interrupted any time, you're on-call, not leading. Block it. Non-negotiable.
- 7KTLO > 25% of your week = something broken. Automation or delegation problem, not a calendar problem.
- 8The first draft is never yours. If you're writing the doc, RFC, or postmortem — you're doing IC work. Someone writes it, you review it.
Weekly Time Budget
40%Deep Workarch, design, hard review
30%Team1:1s, unblocking, planning
20%KTLOmax 25%
10%Adminmax 15%
Ideal Day Structure
9–11Deep work. Architecture, complex review. No meetings. Non-negotiable.
11–12Team. Batch Slack + PRs. Unblock people.
12–13Lunch. Protected.
13–15Meetings, 1:1s, planning. All recurring here.
15–16Follow-ups, async, clear tomorrow's runway.