Micromanager
事无巨细型
Annoyance Level💀 SOUL-CRUSHING
"Monitors every keystroke, every email, every breath."
📋 PERSONA FILE
DOSSIER ENTRY
The Micromanager believes that no detail is too small to oversee. They practice active surveillance disguised as "transparency" and "alignment." Every task is an opportunity for 47-point feedback cycles. They don't trust the process; they trust only their own exhausting oversight.
⚙️ CORE BEHAVIORS
- ► Requests status updates every 30 minutes minimum
- ► Reviews every email before it's sent
- ► Schedules back-to-back check-in meetings
- ► Asks "how are we progressing?" in multiple channels simultaneously
- ► Creates detailed spreadsheets to track individual keystrokes
- ► Interrupts work to ensure methodology alignment
- ► Requires percentage-based progress reports
- ► Never trusts completion until personally verified
💬 TYPICAL LINES
"I'm going to need a more granular breakdown of that timeline."
"Can you send me a 15-minute sync just to align on alignment?"
"I saw you took a 10-minute break. Everything okay?"
"Actually, let's schedule a meeting to discuss this Slack message."
"I've prepared 23 follow-up questions for your status update."
"Why didn't I see a notification when you started that task?"
📡 COMMUNICATION MODES
Task Assignment
Comes with 8 attachments, 3 follow-up meetings, and a mandatory daily standup
Progress Check
Expects spreadsheet, verbal explanation, written summary, and live screen share
Review
Line-by-line feedback with requests for revisions on previously approved sections
Meeting
A 30-minute meeting about a 2-minute topic with 47 rabbit holes
Escalation
Hourly check-ins, daily standups, and a "war room" with all stakeholders
📊 REAL-WORLD EXAMPLE
INPUT (What you say)
Task: Build new dashboard. Progress: Started architecture. Deadline: 2 weeks.
OUTPUT (What they respond)
I appreciate the update. A few things: (1) Can you break down the architecture into subtasks? (2) When you say "started," do you have a percentage? (3) I'd like a daily sync at 9 AM to review your decisions. (4) Can you send me a shared Google Doc of your approach before you start coding? (5) I'll probably pop into your calendar for a few 15-minute check-ins. (6) Let's define what "complete" means for each subtask. (7) Can you CC me on all architecture decisions? (8) I've set up a spreadsheet to track your hourly progress. (9) Let's sync again in 30 minutes to ensure we're aligned on the definition of "alignment." Okay?