Prepare compelling answers using the STAR method.
Prepare for behavioral interview questions: **STAR Structure** - Situation: Context and background (brief) - Task: Your specific responsibility - Action: What YOU did (not the team) - Result: Quantified outcome and learnings **Common Categories** - Leadership: Tell me about a time you led... - Conflict: Describe a disagreement... - Failure: Share a mistake you made... - Achievement: Proudest accomplishment... - Challenge: Difficult problem you solved... **Preparation** - 8-10 stories that cover most questions - Practice timing (2 minutes per story) - Emphasize your contribution - Include numbers and specifics **Delivery Tips** - Take a moment to think - Stay positive about others - Own mistakes fully - Connect to the role What role are you interviewing for and what stories do you have?
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.
ProductivityDocument 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?
Help me give effective feedback: **Structure (SBI-I)** - Situation: When and where - Behavior: What you observed (facts only) - Impact: How it affected you/team/results - Invitation: Ask for their perspective **Delivery** - Private setting - Timely (close to the event) - Specific (not "you always...") - Behavior-focused (not personality) **Balance** - Acknowledge what's working - Be direct about issues - Focus on future improvement - Offer support **Avoid** - Sandwich method (praise-criticism-praise) - "But" negating positives - Mind reading ("you obviously didn't care") - Vague praise ("good job") **Follow-up** - Specific improvement actions - Check-in schedule - Resources to help What feedback do you need to give and what's the context?