CyberSecurity/Soft Skills/Task Planning
Operating Protocol: Work Planning & Execution
This document outlines the standard operating procedure for converting high-level objectives into daily execution, ensuring continuous momentum while buffering against morning operational noise and ad-hoc requests.
System Architecture
The workflow relies on a strict separation of concerns between storage and execution to prevent cognitive overload during deep work blocks.
- System of Record (Digital Task Manager / Jira): Holds the unedited inventory of tickets, monthly goals, study milestones, and backlog items. Manages dates, dependencies, and URLs.
- System of Execution (Kindle Scribe / Notebook): Dedicated solely to the current day's active execution and inbox scratchpad. Sits open on the desk as an immutable focus anchor.
1. Monthly Goals (The Compass)
Monthly goals define the broader strategic targets. These are directional and often represent complete project phases or certification milestones.
- Scope: 2 to 4 major objectives per month.
- Format: Outcome-based.
- Examples: "Complete Domain 4 of study curriculum," "Deploy upgraded WebDesk module," or "Finalize quarterly security audit."
- Review Cadence: Last Friday of the month.
2. Weekly MITs (The Quota)
Weekly Most Important Tasks (MITs) break monthly goals down into a 5-day quota. They define the required outcomes for a successful week but are not used as daily checklist items.
- Scope: 3 to 5 outcomes per week.
- Format: Quotas and deliverables.
- Examples: "Close 3 high-priority tickets," "Study 4 hours total," or "Draft initial remediation notes for new CVEs."
- Review Cadence: Sunday evening or Monday morning before operations begin.
3. Daily Execution (The Engine)
Daily tasks are concrete, non-negotiable execution blocks that advance the Weekly MITs. They must be defined by terminal actions (Draft, Submit, Review, Deploy) rather than open-ended time commitments.
The Daily Operating Timeline
To insulate the daily plan from early morning volatility, the daily lock occurs after the morning team sync.
| Time | Phase | Action Protocol |
|---|---|---|
| 06:30 - 07:00 | Physical Reset & Prep | Zero work chat/email. Ground physical state. Open strictly to a blank E-Paper Scratchpad. Pre-draft a 30-second factual, metric-driven status update. |
| 07:00 - 07:30 | Call / Intake Buffer | Do not edit the daily execution plan. Treat the call as an external audit. Log incoming requests, ticket mentions, or blockers purely as raw bullet points in the Scratchpad margin. |
| 07:30 - 07:35 | Triage & Lock | Run the Scratchpad through the impact filter (Blockers become Task #1; Actionable Work goes to digital backlog; Noise gets ignored). Write down the final 1-3 Daily Actions on the E-Paper. Lock the list. |
Rules of Daily Engagement
- The Rule of 3: Commit to exactly 1 to 3 core actions per day. If these are completed, the day is a success regardless of incoming noise.
- Calendar Anchors: Quota-based tasks (e.g., studying) are protected calendar appointments, not checkbox items.
- Scratchpad Isolation: Ad-hoc requests received during the day are logged in the E-Paper margin, never added to the day's active execution list unless it is a P0 production blocker.
4. Evening Sweep (Shutdown Protocol)
At the end of the workday, perform a 5-minute staging routine to close out the current cycle and prepare the next.
- Process the Scratchpad: Move actionable margin notes into the digital task manager or Jira backlog.
- Clear the Board: Cross off completed daily items.
- Draft Candidates: Pencil in the 1-2 self-directed core actions for tomorrow on a fresh page. Do not finalize until the 07:30 post-standup lock tomorrow morning.
