How to write daily update
Instruction on how to write a daily update in Pulse can be found here.
What is daily update
A daily update is a short, regular post from a team member summarizing what they worked on, what changed, and anything relevant to the team or client.
Purpose
Daily updates build trust through steady, visible progress, removing the need for meetings and status-check messages. A good update lets a client understand, with zero effort, what progress was made on the work that matters to them, with no follow-up questions needed. If they need to ask a follow-up question, the update has failed.
Structure
Daily update template
Done:
- Task description
In progress:
- Task description -> what's ready vs what's left
Blocked (if any):
- Task description -> what we're waiting for and from whom
Include the following
- Tasks completed since the last update, or currently in progress
- For in-progress tasks specify details: what's done, what's in progress, what's not started.
- Any blockers, especially on the client's end, tag the relevant people
Avoid the following
- Vague, general terms with no specifics attached e.g. "bug fixing," "development," "testing," "release prep," "project managing", etc. These are only acceptable with the concrete detail behind them.
- Meetings (internal or with the client)
- Other communication and coordination activities
Examples
Developer's daily update
Done:
- [Pause] The user's_1 status 'pause' or 'resumed' is shown only after the user_2 opens the group again or reopens the app
- [Notifications] Notification is received, but the counter is shown only after the app is reloaded
- [KYC] Clicking the 'Check status' link doesn't open any page
- Investigation of new requirements (upload documents, terms of acceptance)
In progress:
- Onboarding: ACH Debit Auth flow (part 1) - in progress. UI part is ready, ability download documents is in progress
Blockers:
- Access to the account in Google Play Market from @Mark, which is needed to prepare the Android release
QA's daily update
Done:
- Tested tasks on Android+iOS (1.0.0 (34)) dev builds:\
- Delete account: Remove user's info from Stripe
- Bug fixes retesting:\
- [Verify account] 'Upload failed' while uploading document for account verification\
- [KYC] Clicking the 'Check status' link doesn't open any page\
- Add the ability to logout to KYC and Link bank account onboarding steps\
- [Permissions] No permission prompt is shown when uploading a photo in expense\
- [Notifications] Notification is received, but the counter is shown only after the app is reloaded\
- [Pause] The user's_1 status 'pause' or 'resumed' is shown only after the user_2 opens the group again or reopens the app\
- [Admin] 400 error when retry failed payment via Admin panel (comments)
3) Reported new bugs:\
- [Notifications] After the group is deleted all related notifications are deleted too
In progress
- "Edge cases: Charges fail due to insufficient funds/invalid bank account linked". Insufficient funds cases have been already tested on both Android, iOS. Invalid bank accounts are in progress for both iOS and Android.
Blockers
None
Product manager's daily update
Done
Split tasks for refunds and edge cases testing in Linear, add descriptions
Confirmed the text update in the onboarding tutorial, create a task to update it
Checked the new issues reported by Mark on iOS, try to reproduce
Investigations about SSN not required for payers, issue with sign in
Сreated new tasks:
- Group creation Improvement [Linear link]
- Onboarding: ACH Debit Auth flow [Linear link]
In progress
Payment flow requirements are mostly done, just waiting on a few details from Stripe to finalize
Blockers
- Waiting for Stripe's reply on the new payment flow
Designer's daily update
Done
- Prepared the clickable prototype for user's auth settings [link]
- Prepared new onboarding authorization screens on Lovable [link]
- Prepared the new version of the onboarding screen with documents in Lovable [link]
In progress
None
Blockers
None