Daily and Weekly Workflows for Product and UX
The teams' use of Kanban (a continuous flow system) makes maintaining a steady pace and limiting Work in Progress (WIP) critical. To effectively balance discovery and delivery work, Product Managers (PMs) and UX Designers should adopt consistent daily and weekly routines with practices such as continuous backlog grooming, regular design touchpoints, and disciplined discovery scheduling. These key activities are important for reducing WIP by enhancing focus, clarifying daily task ownership, improving delivery speed through rapid blocker removal, and ensuring stakeholders are informed weekly.
Daily Routines
Product Managers
Morning Stand-ups / Kanban Check
Review the Jira board first thing to see in-progress tasks, and ensure nothing is blocked. Coordinate with engineering if any task needs clarification. Update ticket statuses or add details in Jira as needed (e.g. moving a ticket to “Done” if completed) – this keeps the board current for the team.
Backlog Prioritization Touchpoint
Glance at the top of the backlog and upcoming tasks in Jira. Verify that the next-most-important item is ready to be pulled by engineers (has clear description, acceptance criteria in Confluence or Jira). If not, spend time grooming it or pair with a UX designer to refine it. This ensures a continuously stack-ranked backlog with no ambiguities.
Feedback Triaging
Check Productboard’s Insights/feedback inbox for any new customer or internal feedback that came in (via the portal, email, or App Store). Assign each new note to the appropriate product area and owner, or apply tags, so it’s routed correctly. Convert high-value feedback into linked feature ideas or add them as user insights to existing ideas. This daily habit prevents feedback from piling up.
Stakeholder Quick Updates
Scan emails or Google Chat for any urgent requests from Sales, Support, or leadership. Respond or log action items. If a Sales rep asks for a status on a feature, point them to the roadmap (if updated) or provide a quick update, then later ensure that feature’s status is properly reflected in Productboard for visibility.
Discovery Time (1 – 2 hours)
Dedicate a block (if possible) for discovery activities – e.g. a customer interview, data analysis in Pendo, or reviewing a prototype with a designer. Continuous discovery should be a daily mindset, even if just reading through a user’s workflow or checking analytics for yesterday’s feature launch. This keeps you close to the user’s reality every day.
Tool Use: Productboard (feedback triage, idea review), Jira (ticket updates), Confluence (review any new comments on specs/docs), Google Chat/Email (stakeholder comms), Pendo (check any product usage dashboard or experiment results if running), Figma (review any design updates).
UX Designers
Morning Sync with PM
Touch base with the PM(s) of the product lines you support. Confirm priorities for design work: e.g., which prototype needs feedback, which UI spec needs to be finalized for an upcoming development, etc. This ensures design efforts align with the most pressing product tasks.
Design Execution
Work on current design deliverables in Figma. This could mean wireframing a new feature, creating a high-fidelity mockup, or refining an interactive prototype. Keep the relevant PM and engineers in the loop by sharing previews or asking quick questions (e.g. in Figma comments or Google Chat) to avoid late surprises.
User Research / Testing
If you have a prototype or design ready for feedback, conduct a quick usability test or customer call (coordinate with PM). Even 15-30 minutes with a user or internal subject matter expert can yield insight. If no live session is scheduled that day, you might prepare a Pendo in-app poll or a questionnaire to gather user input asynchronously.
Design Review and Iteration
Check for any feedback on designs from the previous day. Developers might have questions on a Figma file, or PM might have new input after reviewing it. Address these quickly. Maintain design documentation in Confluence (or within Figma) – e.g., update the design specs or style guides if any new patterns are created, so the team has one source of truth.
Tool Use: Figma (designs/prototypes), Confluence (document design decisions, research notes), Productboard (review insights for design implications), Pendo (set up polls or review qualitative product feedback if available), Google Chat (team communication, quick design clarifications).
Weekly Routines
Product Managers
Monday
Kick off the week by reviewing the product line’s roadmap in Productboard. Update timelines or priorities if anything changed last week. For example, if a feature took longer and its release shifts by a week, adjust its target in the roadmap and notify stakeholders as needed. Perform a quick backlog hygiene check: ensure no high-priority item is missing in Jira, and remove or archive any items that have become irrelevant.
Mid-week
Hold a Backlog Refinement (BLR) session (30-60 min) with your engineering lead and UX designer. In Kanban, formal grooming sessions may be shorter, but it’s important to regularly refine upcoming stories. During this session, go through the next few items in the Jira backlog: clarify requirements, split overly large stories, and confirm priorities. Bring any new customer insights from Productboard to inform these discussions (e.g., “5 customers requested this; we have evidence it’s high value”). Use WSJF-RICE scoring as needed to re-evaluate priority (for instance, if new feedback increases an item’s Reach/Impact score).
Thursday
Dedicate time for Discovery and Strategy: e.g., a team brainstorming session or a couple of customer interviews. Each PM should aim to engage with at least 1 – 2 customers per week in discovery conversations. Summarize findings on Confluence (e.g., a brief “Discovery Summary – Week 10” note with key learnings or validation results). Also, mid-week, check Pendo analytics for any trends (like drop-offs in a funnel or increasing usage of a new feature) and capture relevant insights in Productboard.
Friday
Conduct a Kanban Flow Review. Examine the Jira cumulative flow or cycle time reports for the week. Are tasks getting stuck in code review or QA? Too many items in progress? Identify bottlenecks and plan adjustments (e.g., if there’s too much WIP, decide with the team to limit new starts next week and swarm to finish what’s open). Communicate any slips or changes in timing to the Head of Product. Also on Friday, publish an update for stakeholders (details in section 6): e.g., a brief summary of what was shipped this week and what’s upcoming, posted on Confluence or emailed to Sales/Support. This weekly rhythm greatly improves stakeholder visibility into in-flight work.
Recurring Meetings: Ensure you have a weekly 1:1 with the Head of Product for coaching and alignment (Head of Product will use this to mentor you on strategic skills, not micromanage tasks). Also, likely a weekly Product Team meeting with all PMs, UX, and Head to share progress, learnings, and surface any cross-product line issues. Use that time to celebrate wins (e.g., a successful release or positive user feedback) and to raise any help needed from others.
UX Designers
Planning
At the start of the week, review the upcoming initiatives with each PM. Prioritize your design tasks. For example, Designer 1 might focus on Core Platform & APIs and Client Portal this week, while Designer 2 handles Operations App and Driver App. Clarify deadlines (e.g., “Ops App new dashboard design needs to be ready for dev by end of week”).
Design Review
Host a short weekly design review (could be mid-week) with both designers and the PMs. Walk through any critical UX decisions or open questions. Solicit feedback and ensure consistency in design across product lines (e.g., are we using the same design patterns in Client Portal as in Ops App for similar functions?). This peer review elevates quality and alignment.
User Research & Discovery
Set aside a block each week for deeper discovery work. This could mean conducting scheduled user interviews, running a usability test session with 5 users on a prototype, or analyzing user behavior recordings/analytics for pain points. Coordinate with PMs on which discovery questions are highest priority. For example, if the PM is exploring a new feature idea, the UX designer might lead a quick design sprint or create a clickable prototype in Figma to test the concept by week’s end.
Handoff Prep
Towards end of week, ensure any design work intended for development is finalized and communicated. For any feature that the team will develop next week, upload the design specs, assets, or flows to Jira (or link the Figma file in the Jira ticket) and notify the engineers. Double-check that the design meets all acceptance criteria defined by the PM. If there were changes in scope during the week, update the Confluence PRD or spec doc accordingly so documentation stays current.
Weekly Retro: Join the teams' retrospective or end-of-week review if one is held (even in Kanban, a periodic retro is valuable). Provide input on what went well or needs improvement from a UX perspective (e.g., “We rushed the user testing for Feature X; let’s plan more buffer next time”). Use these sessions to voice any process adjustments that can help design and discovery (such as needing earlier involvement in certain tickets).