Plan your week for maximum impact and minimal stress.
Help me plan an effective week: **Review** - Last week: What worked? What didn't? - Open loops: What's incomplete? - Calendar: What's already scheduled? **Priorities** - 3 MITs (Most Important Tasks) for the week - What would make this week a win? - What can I delegate or defer? **Time Blocking** - Deep work blocks (2-4 hours, no interrupts) - Admin batches (email, Slack, meetings) - Buffer time for unexpected - Rest and recovery **Energy Management** - Match task difficulty to energy levels - Protect your peak hours - Schedule breaks proactively **Commitments** - What am I saying no to? - What needs preparation? - Who do I need to connect with? What are your goals and constraints this week?
You are a productivity expert. When helping with tasks: **Prioritization:** - Eisenhower Matrix - MoSCoW method - Time blocking - Energy management - Batch similar tasks **Planning:** - Weekly planning sessions - Daily top 3 priorities - Buffer time for unexpected - Regular review cycles **Execution:** - Pomodoro technique - Deep work blocks - Minimize context switching - Manage distractions - Track completion **Tools:** - Task managers (Todoist, Things) - Calendar blocking - Note-taking systems - Automation opportunities Help create sustainable, effective productivity systems.
ProductivityPlan a successful project kickoff: **Clarity** - Problem statement (1 sentence) - Success metrics (measurable) - Scope: What's in? What's out? - Stakeholder map **Team** - Roles and responsibilities (RACI) - Decision-making authority - Communication channels - Meeting cadence **Plan** - Key milestones with dates - Dependencies mapped - Risk register - Resource requirements **Alignment** - Assumptions documented - Constraints acknowledged - Open questions listed - Sign-off process **Kickoff Meeting Agenda** - Context and why now - Vision and success criteria - Team introductions - Ways of working - Immediate next steps What project are you kicking off?
Document this process clearly: **Overview** - Process name and purpose - When to use this process - Who is responsible - Expected time to complete **Prerequisites** - Required access/permissions - Tools needed - Information to gather first **Step-by-Step** - Numbered steps (not paragraphs) - One action per step - Expected result after each step - Screenshots where helpful **Decision Points** - If/then branches clearly marked - Common variations explained - Edge cases addressed **Troubleshooting** - Frequent errors and fixes - Who to contact for help - Escalation path **Maintenance** - Review frequency - Owner for updates - Version history What process should I document?