Daily Dev Update (CQ)¶

Owner: Vi | Updated: 2026-02-05

Purpose¶

Post a brief end-of-day update so leadership can help you move faster. This is not surveillance—it's how you get blockers cleared overnight.

The timezone works for you:

You post at 6pm VN → Erik sees it at 7am US
He responds → You wake up to answers at 9am VN

Blockers posted today = answers waiting tomorrow.

Who¶

All CQ developers.

When¶

Every working day, before you log off (around 6pm VN).

Takes < 2 minutes.

Where¶

#cq-product channel (the main one with Erik, not #cq-vn).

English only. Keep it brief.

The Template¶

Copy and fill in:

**[Your Name] - [Date]**

**Working on:** [Task name from ClickUp]
**Status:** [On track / Blocked / Need input]
**Progress:** [1 sentence - what you did today]
**Tomorrow:** [1 sentence - what you'll do next]
**Blocker:** [None / Describe blocker + what you need]

Examples¶

Good: On Track¶

**Minh - Feb 5**

**Working on:** User dashboard redesign
**Status:** On track
**Progress:** Completed responsive layout for mobile view
**Tomorrow:** Add data fetching and loading states
**Blocker:** None

Good: Blocked (This Gets You Help)¶

**Linh - Feb 5**

**Working on:** Payment integration
**Status:** Blocked
**Progress:** Set up Stripe SDK, tested sandbox mode
**Tomorrow:** Connect to backend (if unblocked)
**Blocker:** Need API endpoint specs from backend. Who owns this?

Good: Need Input (Not Blocked, But Need Direction)¶

**Tuan - Feb 5**

**Working on:** Search feature
**Status:** Need input
**Progress:** Built basic search, works for exact matches
**Tomorrow:** Depends on answer below
**Blocker:** Should search include fuzzy matching? Will add 2 days. Worth it?

What Each Status Means¶

Status	Meaning	What Happens
On track	No issues, progressing normally	Leadership sees progress, no action needed
Blocked	Can't continue without help	Someone will respond to unblock you
Need input	Can continue, but need decision	Product/leadership will weigh in

Rules¶

DO¶

Post every day you work (no exceptions)
Be honest about blockers (stuck = signal, not failure)
Post in #cq-product (not #cq-vn)
Keep it brief (the template is enough)
Post before you log off

DON'T¶

Wait until morning to post yesterday's update
Hide blockers (costs YOU time)
Write essays (brief is better)
Skip days (silence = concern)

Why This Matters¶

For you: - Blockers get cleared faster (overnight vs next-day meeting) - Leadership can help prioritize when you're unsure - No one assumes you're stuck if you're actually on track

For the team: - Erik can see progress without asking - Vi doesn't have to relay messages - Problems surface early, not at deadline

What Happens If You Don't Post¶

| Day 1 | Vi will DM you asking for update | | Day 2 | Ryan gets notified | | Day 3+ | Erik gets notified—this is a serious concern |

Silence is the problem, not being stuck. We'd rather hear "I'm blocked and don't know what to do" than hear nothing.

FAQ¶

Q: What if I have nothing to report? A: Post anyway. "On track, continued work on X, no blockers" is fine.

Q: What if I'm stuck but embarrassed? A: Post it. Being stuck is normal. Hiding it wastes YOUR time. We want to help.

Q: Can I post in Vietnamese? A: No. Erik needs to read it. Keep it simple English—doesn't need to be perfect.

Q: What if I work late (past 6pm)? A: Post when you actually stop working. The point is "end of your day."

Q: Do I post on days I'm mostly in meetings? A: Yes. "In meetings all day, no dev progress, will resume X tomorrow."

Q: What if my task spans multiple days? A: That's normal. Each day just say what you accomplished on it.

Quick Reference¶

Channel: #cq-product Time: End of day (~6pm VN) Language: English Length: < 2 minutes to write

Template:

**[Name] - [Date]**
**Working on:**
**Status:** On track / Blocked / Need input
**Progress:**
**Tomorrow:**
**Blocker:**