Laporan dan Presentasi Kantor

Bantu saya susun executive summary 1 halaman.

Source material:
- Laporan asli: [paste atau deskripsikan, konteks panjang]
- Audience target: [exec, board, decision maker]
- Decision yang dibutuhkan: ...

Bantu saya susun executive summary 1 halaman.

Source material:
- Laporan asli: [paste atau deskripsikan, konteks panjang]
- Audience target: [exec, board, decision maker]
- Decision yang dibutuhkan: [konteks]
- Time budget reader: [estimasi mereka punya berapa menit]

Output executive summary structure:

Header (1 baris):
- Title yang spesifik
- Date
- Author / department
- Confidentiality level (kalau ada)

Section 1 — Bottom line up front (50 kata):
- Yang harus reader tahu kalau cuma baca 1 paragraf ini
- Specific number / outcome
- Critical decision needed

Section 2 — Context (50 kata):
- Why this report exists
- Trigger event / question yang dijawab
- Scope (apa yang covered, apa yang TIDAK)

Section 3 — Key findings (max 3 bullet, 30 kata each):
- Yang paling impactful
- Backed dengan angka
- Tidak nuance overload

Section 4 — Recommendation (max 3, 30 kata each):
- Specific action (bukan "consider", "explore")
- Owner (siapa yang harus eksekusi)
- Timeline
- Resource needed

Section 5 — Risk + dependencies (40 kata):
- Top 1-2 risk
- Critical assumption
- Decision dependencies

Section 6 — Next step (30 kata):
- Apa yang reader harus do
- Kapan decision needed
- Reference ke full report

Footer:
- Page reference ke detail di full report
- Contact untuk Q&A

Aturan global:
- Maks 1 halaman cetak A4
- Font readable (11pt min)
- White space generous
- Heading + sub-heading clear
- Bullet > paragraf

Anti-pattern:
- "This report covers..." opening (waste line)
- Hedge everything ("It is likely that perhaps possibly...")
- Cover all 50 nuance (exec wants signal, not noise)
- Recommendation generic ("We should improve communication")

Tone:
- Confident tapi tidak overclaiming
- Specific, bukan vague
- Action-oriented
- Politely direct

Bantu saya susun deck presentasi quarterly review.

Konteks:
- Audience: [exec / department head / cross-functional]
- Quarter: [Q1/Q2/Q3/Q4]
- Department: [sales / marketing / product / ops]
- Durati...

Bantu saya susun deck presentasi quarterly review.

Konteks:
- Audience: [exec / department head / cross-functional]
- Quarter: [Q1/Q2/Q3/Q4]
- Department: [sales / marketing / product / ops]
- Duration: [15 menit / 30 menit / 45 menit]
- Goal: [report progress / decision / budget request / strategic alignment]

Output deck structure (10-15 slides):

Slide 1 — Title:
- "Q[X] Review - [Department Name]"
- Date + presenter
- Hindari logo bertumpuk

Slide 2 — TL;DR (1 slide, executive summary):
- 3 key wins
- 1 key challenge
- 1 strategic ask
- Format: bullet, large font

Slide 3 — Goals recap:
- Apa yang ditargetkan di awal Q
- Visual: bar chart goal vs actual
- Color: green achieved, amber partial, red missed

Slide 4-6 — Wins deep-dive (1 slide per major win):
- What we achieved
- Quantified impact
- How (briefly)
- Visual support

Slide 7 — Misses / challenges (1 slide):
- Yang gak achieve + alasan honest
- Mitigation yang lagi jalan
- Adjusted target

Slide 8-10 — KPIs trending:
- 3-5 key metric dengan trend line
- YoY atau QoQ comparison
- Annotate moment yang significant

Slide 11 — Customer / market insight (kalau relevant):
- Voice of customer
- Trend di market yang impact
- Competitive position

Slide 12 — Resource utilization:
- Budget actual vs plan
- Headcount status
- Tools / tech investment

Slide 13-14 — Next quarter plan:
- Top 3 priority
- Specific outcome target
- Resource needed
- Risk + mitigation

Slide 15 — Asks + decision needed:
- Specific decisions dari exec
- Budget approval
- Hire approval
- Strategic alignment confirmation

Appendix slides:
- Detail data per KPI
- Methodology
- Backup untuk question

Aturan:
- 1 idea per slide (bukan bullet point dump)
- Headline statement (declarative)
- Visual > text
- Chart pakai 1 highlight color (rest grey)
- Source citation kalau pakai external data

Speaker notes:
- Apa yang harus dibilang per slide
- Pertanyaan yang anticipated
- Backup data untuk follow-up Q

Anti-pattern:
- Slide yang gabung 5 chart kecil-kecil
- All-text slide tanpa visual
- Slide yang dibaca verbatim presenter
- "Thank you, Questions?" sebagai last slide (boring)

Bantu saya tulis email update project mingguan ke stakeholder.

Konteks project:
- Project name: [konteks]
- Phase saat ini: [konteks]
- Stakeholder list: [exec / sponsor / cross-func / external]
- Ti...

Bantu saya tulis email update project mingguan ke stakeholder.

Konteks project:
- Project name: [konteks]
- Phase saat ini: [konteks]
- Stakeholder list: [exec / sponsor / cross-func / external]
- Timeline: [start - end date]
- Status saat ini: [on-track / at-risk / off-track]

Data update minggu ini:
- Milestone yang completed: [list]
- Milestone yang missed: [list]
- Blocker: [list]
- KPI: [data]
- Decision needed: [list]

Output email format:

Subject line:
- "[Project Name] Update - Week [X] - [Status]"
- Status di subject (Green / Amber / Red)
- Avoid clickbait

Body:

Opening (50 kata):
- Status overall (Green/Amber/Red dengan reason)
- Yang harus reader tahu kalau cuma baca 1 paragraf

Section 1 — Progress (bullet):
- What was completed (specific)
- Quantified impact
- Compared to plan

Section 2 — Issues (kalau ada):
- What's blocked / at-risk
- Impact ke timeline atau scope
- Mitigation yang lagi dilakukan
- Help yang dibutuhkan

Section 3 — Next week priority:
- Top 3 priority
- Critical milestone
- Resource utilization

Section 4 — Decisions needed:
- Specific decision dari stakeholder
- Deadline untuk decision
- Implication kalau di-delay

Section 5 — Numbers (kalau ada KPI):
- Current vs target
- Trend (improving / stable / declining)

Closing:
- "Reply with any question"
- Office hour offer (kalau senior stakeholder)
- Reference ke project doc / dashboard

Aturan:
- Max 200 kata total
- Visual: status badge (🟢🟡🔴 atau colored text)
- Honest about issues (jangan sugarcoat amber jadi green)
- Action-oriented (bukan storytelling)
- Cadence: 1 email per minggu, hari sama, jam sama

Anti-pattern:
- "Things are going well" tanpa data
- Burying bad news di paragraf 3
- Vague seperti "We're making progress"
- Forward email panjang yang ada di thread
- "Please find attached" tanpa konteks

Bonus per email:
- 1 line celebration achievement spesifik
- Mention nama team member yang excellent (recognition)

Bantu saya susun notulen meeting yang actionable.

Konteks meeting:
- Tipe: [decision-making / brainstorm / update / review]
- Attendee: [count + roles]
- Duration: [menit]
- Agenda: [topic list]

Out...

Bantu saya susun notulen meeting yang actionable.

Konteks meeting:
- Tipe: [decision-making / brainstorm / update / review]
- Attendee: [count + roles]
- Duration: [menit]
- Agenda: [topic list]

Output notulen structure:

Header:
- Meeting title
- Date + time + duration
- Location (in-person / virtual link)
- Attendees: name + role + present/absent
- Note taker: nama

Section 1 — Meeting purpose (1 sentence):
- Apa yang ingin di-decide / discussed / aligned

Section 2 — Decisions made (highest priority section):
| # | Decision | Rationale | Decided by | 
- Specific (bukan "we discussed X")
- Decision-maker named
- Brief rationale

Section 3 — Action items (table):
| # | Action | Owner | Due Date | Priority | 
- Verb-first action (kirim, review, draft, decide)
- 1 owner per action (bukan tim)
- Specific due date (bukan "next week")
- P0/P1/P2 priority

Section 4 — Open questions / unresolved:
- Yang belum bisa decide hari ini
- Apa yang dibutuhkan untuk decide nanti
- Follow-up owner + timeline

Section 5 — Risks / dependencies discussed:
- Yang muncul di meeting
- Mitigation yang lagi explore

Section 6 — Key insights / context (optional):
- Yang penting untuk reader yang absent
- Bukan transcript verbatim
- Insight, bukan dialogue

Section 7 — Next meeting:
- Date + time + agenda preview
- Pre-read kalau ada

Aturan notulen efektif:
- Distribusi: max 2 jam setelah meeting (sebelum lupa)
- Format: scannable, table-heavy
- Notes < action items ratio (50:50 max)
- Quote verbatim hanya kalau decision spesifik
- Anonymize sensitive points kalau distribusi luas

Anti-pattern:
- Transcript dialog ("John said... Mary replied...")
- Generic action ("follow up", "look into")
- Tanpa owner / deadline
- Notulen yang lebih panjang dari meeting

Tools recommendation:
- Live note: bullet di doc waktu meeting
- Polish: 30 menit setelahnya
- Distribute: email + project tool

Bonus: 3 hal yang HARUS muncul di notulen meeting decision (legal/compliance importance).

Bantu saya tulis self-assessment performance review.

Konteks:
- Periode review: [tahun / kuartal]
- Role saya: [konteks]
- Goal yang ditetapkan di awal: [konteks]
- Achievement saya: [list konkret de...

Bantu saya tulis self-assessment performance review.

Konteks:
- Periode review: [tahun / kuartal]
- Role saya: [konteks]
- Goal yang ditetapkan di awal: [konteks]
- Achievement saya: [list konkret dengan angka]
- Challenge yang dihadapi: [list]
- Growth area yang teridentifikasi: [list]

Output self-assessment:

Section 1 — Year/Quarter Summary (100 kata):
- Top 3 contribution yang impact bisnis
- Quantified outcome
- Stakeholder yang affected positively

Section 2 — Goal achievement (per goal):
- Goal original (verbatim dari awal periode)
- Achievement aktual (specific, dengan angka)
- Status: exceeded / met / partial / missed
- Konteks kalau partial / missed (honest, bukan excuse)

Section 3 — Wins beyond goals:
- Initiatives yang dilakukan diluar formal goals
- Cross-functional collaboration
- Process improvement
- Mentorship / knowledge sharing

Section 4 — Challenges + how I navigated:
- 2-3 challenge utama
- Action yang taken
- Outcome
- Lesson learned

Section 5 — Growth areas (self-aware):
- 2-3 skill / behavior yang masih grow
- Specific evidence
- Plan untuk improve
- Support yang dibutuhkan dari manager

Section 6 — Feedback yang saya appreciate:
- Specific feedback yang impactful
- Bagaimana saya act on it

Section 7 — Next period focus:
- Top 3 area focus
- Stretch goal kalau ada
- Resource / support request

Section 8 — Asks (kalau relevant):
- Career trajectory discussion
- Promotion consideration
- Compensation review
- Specific opportunity (project / mentor / training)

Aturan self-assessment:
- Specific > general ("Increased team velocity 30%" > "improved team productivity")
- Quantify everything possible (revenue, time, count, %)
- Use STAR (Situation, Task, Action, Result)
- Tidak undersell (perempuan + minority sering)
- Tidak overclaim (manager akan kasih reality check)
- Honest tentang growth area (signal maturity)

Anti-pattern:
- "I worked hard on..." (work hard tidak measurable)
- "We achieved..." tanpa specify role kamu
- Vague seperti "improved team morale"
- Skip growth area (looks defensive)
- Compare ke kolega negatively

Bonus: 5 pertanyaan untuk diskusi dengan manager saat review meeting.

Saya butuh pitch atasan untuk approval initiative.

Konteks:
- Yang saya minta: [budget / hire / project / strategic decision]
- Atasan profile: [data-driven / vision-led / risk-averse]
- Time slot: [...

Saya butuh pitch atasan untuk approval initiative.

Konteks:
- Yang saya minta: [budget / hire / project / strategic decision]
- Atasan profile: [data-driven / vision-led / risk-averse]
- Time slot: [menit]
- Format: [in-person / written / hybrid]
- History: [first pitch atau iteration]

Output pitch structure:

Pre-meeting:
- 1-page pre-read (kirim 24 jam sebelum):
  - Problem statement
  - Solution overview
  - Decision needed
  - Time/resource ask
- Anticipate top 3 question

Meeting flow:

Menit 1-2 — The ask (lead with it):
- Specific request (bukan "I want to propose...")
- Why now (timing trigger)
- Decision deadline

Menit 2-5 — Problem framing:
- Why this matter ke business (their language)
- Cost of doing nothing
- Strategic alignment

Menit 5-10 — Solution:
- Approach overview
- Alternative considered + why rejected
- Resource + timeline

Menit 10-13 — Expected outcome:
- Specific KPI / metric
- ROI estimate (kalau possible)
- Long-term implication

Menit 13-15 — Risk + mitigation:
- Top 2-3 risk
- Mitigation plan
- Kill criteria (kapan kita stop)

Q&A (5 menit):
- Anticipated question:
  - "What if it doesn't work?"
  - "Why this approach vs other?"
  - "Why now vs later?"
  - "Why you / your team?"

Closing:
- Restate ask
- Specific decision needed
- Next step kalau approved + kalau ditolak

Aturan persuasion:
- Lead with their priority (apa yang atasan care)
- Speak their language (data-driven vs vision)
- Numbers > adjectives
- Acknowledge their concern proactively
- Confident tapi tidak arogan

Common mistake:
- Start with backstory (atasan tidak punya patience)
- Hedge everything ("I think maybe possibly")
- Beg ("please please consider")
- Defensive ke pertanyaan (sounds insecure)
- Tidak prepare alternative kalau no

Backup plan:
- Plan B kalau full ask ditolak
- Smaller pilot proposal
- Trial period option
- Different resource ask

Anti-pattern delivery:
- Read slides verbatim
- Apologize berlebihan
- Sebut "I'm not sure but..."
- Avoid eye contact

Bonus: 3 phrase yang efektif untuk handle pushback tanpa kelihatan defensive.