Fathom Intake — 2026-04-18

create in project High usage for "Find" (sourcing shippers), but near-zero adoption for "Track & Reach" (follow-up/CRM). 90% summary+transcript

Hypothesis	Focus all resources on activating existing users.
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, They
Project	546966ce-a9c5-42ac-aa91-974816e14084
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket identifies a segment ('existing users') and mentions adoption metrics, but does not clearly specify a named user/customer/segment experiencing a particular pain point. It references a feature disparity ('Find' vs 'Track & Reach') rather than articulating a specific pain point the users experience.
hypothesis	❌		The description states a directive ('Focus all resources on activating existing users') but does not include a proposed direction, hypothesis, or solution explanation for why this approach would address the adoption problem.
time_budget	❌	Yes	No explicit time-budget (hours/days/weeks/cycles), priority level (P0-P2), or deadline mentioned. The ticket describes a strategic goal but lacks concrete temporal or urgency signals needed for scheduling.
test_plan	❌		The ticket describes a high-level strategy to focus resources on user activation but contains no specific validation plan referencing real users, customers, or live data. There are no mentions of testing with named individuals, checking specific analytics, or validating against actual customer data.
ticket_completeness	❌	Yes	Title meets criteria (a) with 4+ meaningful words. Description fails criteria (b) - only 1 sentence provided. No acceptance criteria, deliverables, or definition of done present, failing criteria (c).

create in project Lack of systematic process to translate customer research and insights into actionable problems for the next development cycle. 65% transcript_only

User context	Shan Wu (founder) is conducting customer calls to validate product positioning around Ghost Rider AI, but struggles to capture and organize learnings into structured work items for the team.
Hypothesis	Build a process or tool to assist in harvesting customer insights from calls/notes and translating them into a prioritized problem list that can be worked on in the next cycle.
Time budget	next cycle (appears to be weekly planning cycle)
Deliverable	80% of next cycle's problem list identified, with potential process improvement for converting customer notes into actionable work items.
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Late, Otherwise, Makes, Energy, Cyro, Yep, Hopefully, Feel, Louise Dungca (Linear:457821c6-bea0-49ae-8bf8-3bc892bf7c12, Slack:U07GYNH7JS2), Hmm, Two, Awesome, Calling, Biggest, Ghost Rider, Cool, You
Project	e0c07324-6699-4cd7-b05d-e0a5465f220f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named user: Shan Wu (founder). Pain point: struggles to capture and organize learnings from customer calls into structured work items for the team.
hypothesis	✅		The ticket includes a proposed direction: 'Build a process or tool to assist in harvesting customer insights from calls/notes and translating them into a prioritized problem list.' This is a clear 'we think the solution is X' statement, though it presents it as a general direction rather than a highly specific hypothesis.
time_budget	✅	Yes	Contains explicit time-budget signal ('next cycle'), clear deliverable ('80% of next cycle's problem list identified'), and implies urgency through founder involvement and process improvement scope
test_plan	✅		The ticket explicitly references Shan Wu (founder) conducting customer calls and needing to capture learnings from those real calls/notes. It specifies validating against actual customer research and positioning feedback, with a concrete deliverable of '80% of next cycle's problem list identified' based on real customer insights from calls.
ticket_completeness	✅	Yes	Title has 6 meaningful words describing a systematic process gap. Description provides 2+ sentences of context about Shan Wu's customer calls and the organizational challenge. Deliverable clearly defines 'done' as 80% of next cycle's problem list identified plus process improvement for converting notes to work items.

create in project Team is spending time building features without sufficient customer discovery and validation. 65% transcript_only

User context	The product team (including Hakeem) is building features without clear understanding of user needs, leading to potentially random or unfocused product development.
Hypothesis	Shift team focus from building to conducting more customer conversations to validate assumptions and understand real problems before development.
Time budget	next week's site call
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Fathom, You, Otherwise, Focus, Hakiem Aulia (Linear:1ca29403-c25e-4b6e-b952-47881d3ce0d2, Slack:U06T1PFJHKQ)
Project	9d0bb435-b894-400a-87af-394b0de57c72
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	Contains a named user (Hakeem) and team reference, but lacks a specific pain point. The description is vague about what actual problems users face—it only states that features are being built without understanding needs, without articulating a concrete pain point users experience.
hypothesis	✅		The description includes a clear proposed direction: 'Shift team focus from building to conducting more customer conversations to validate assumptions and understand real problems before development.' This is a hypothesis about the solution (more customer discovery before building).
time_budget	✅	Yes	Contains explicit time-budget signal: 'next week's site call' indicates a deadline within the next week, which is a clear temporal constraint for this initiative.
test_plan	❌		The ticket describes a general problem and proposes a shift in approach, but does not include a specific validation plan that references a real user, customer, or live data. 'Next week's site call' is too vague and doesn't name specific people or concrete validation methods.
ticket_completeness	❌	Yes	Title is sufficient (5 meaningful words). Description has 2 sentences of context. However, there are no explicit acceptance criteria, deliverables, or definition of 'done' - only a vague directive to 'shift focus' and a budget mention. The ticket lacks concrete, measurable outcomes.

create in project Unclear what outcomes and next steps should be defined when problem owners are engaged for problem discovery calls. 55% transcript_only

User context	Problem owners who have specific goals they want to focus on, but blockers and user pain points are not well-defined.
Hypothesis	Structure discovery calls around identifying specific blockages users face in achieving their stated goals, with a concrete 'offer' or solution as the outcome.
Time budget	one week for team to conduct calls
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Time, Let, Who, Forward Labs, Then, Offer
Project	e0c07324-6699-4cd7-b05d-e0a5465f220f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket identifies 'problem owners' as a segment but does not name a specific user, customer, or segment. While it mentions 'user pain points' as a general concept, it does not describe a specific pain point that users experience. The ticket is about process/methodology rather than addressing a concrete user problem.
hypothesis	✅		The ticket includes a proposed direction: 'Structure discovery calls around identifying specific blockages users face in achieving their stated goals, with a concrete 'offer' or solution as the outcome.' This describes how the team should approach the problem discovery calls.
time_budget	✅	Yes	Contains explicit time-budget signal: 'one week for team to conduct calls'
test_plan	❌		The ticket describes a discovery process and mentions conducting calls with problem owners, but does not specify validation against real users, customers, or live data. It lacks concrete details like 'speak with [specific person]', customer names, or metrics to measure outcomes post-implementation. The budget allocation does not constitute a validation plan.
ticket_completeness	✅	Yes	Title has 15 meaningful words exceeding the 4-word minimum. Description contains 2 sentences providing context about the problem and approach. Acceptance criteria are present: structure calls around identifying blockages, define concrete outcomes/solutions, and complete within one week budget.

create unclassified Team members lack sufficient resources and clarity to execute on strategic goals, requiring targeted enablement beyond what can be provided 50% transcript_only

User context	Hakim, a team member with a clear KPI around OAuth implementation that is strategic to the company
Hypothesis	For well-defined, strategic KPIs with clear owners, the primary blocker is execution through outreach (calling people) rather than additional resource enablement
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Hakim, You, Two, Hakiem Aulia (Linear:1ca29403-c25e-4b6e-b952-47881d3ce0d2, Slack:U06T1PFJHKQ)
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named user 'Hakim' is identified (a), and the specific pain point is clearly stated: lack of execution resources and clarity to meet strategic goals, with the primary blocker being execution through outreach rather than resource enablement (b).
hypothesis	❌		The ticket description identifies a problem (lack of resources and clarity) and mentions a specific example (Hakim's OAuth KPI), but does not include a clear proposed direction, hypothesis, or 'we think the solution is X' statement. The description focuses on stating the blocker (execution through outreach) rather than proposing a solution approach.
time_budget	❌	Yes	No explicit time budget (hours/days/weeks), no priority level (P0/P1/P2), and no clear deadline mentioned. The ticket describes a problem and context but lacks concrete temporal or urgency signals.
test_plan	❌		The ticket mentions 'Hakim' as a team member with an OAuth KPI, but does not include a specific validation plan that references real users, customers, or live data for testing. It describes a problem (lack of resources/clarity) but lacks concrete validation steps like 'test OAuth with Hakim', 'verify implementation with X customers', or 'measure KPI progress post-implementation'.
ticket_completeness	❌	Yes	Title meets criteria (a) with ≥4 meaningful words. Description fails criteria (b) - it contains only sentence fragments and context clues, not ≥2 complete sentences explaining the problem. No acceptance criteria, deliverables, or definition of 'done' present, failing criteria (c).

create in project Team members lack clear problem ownership and there is a disconnect between user learnings from calls and actual work being executed 55% transcript_only

User context	Forward Labs team members and internal stakeholders who are not clear on what problems they own, and users whose feedback from calls is not being acted upon
Hypothesis	Shift from cycle-based planning to week-by-week planning and focus the company on identifying and pushing the most important levers
Time budget	week by week
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Etienne Auroux (Linear:e8f6c396-4921-4362-ab74-d6beb0bceada, Slack:U095GPK0YF5), Today, Rice
Project	e0c07324-6699-4cd7-b05d-e0a5465f220f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	While the ticket names users (Forward Labs team members, internal stakeholders, users), it lacks a specific named user, customer, or segment. The pain points mentioned are vague ('lack clear problem ownership', 'disconnect between learnings and execution') rather than specific concrete problems with measurable impact.
hypothesis	✅		The description includes a proposed direction: 'Shift from cycle-based planning to week-by-week planning and focus the company on identifying and pushing the most important levers.' This is a clear statement of the proposed solution to address the problem ownership and feedback disconnect issues.
time_budget	✅	Yes	Contains explicit time-budget signal: 'week by week' planning mentioned in description and 'Budget: week by week' in metadata
test_plan	❌		The ticket describes a high-level organizational problem and proposes a planning approach shift, but contains no specific validation plan referencing real users, customers, or live data. There are no mentions of reaching out to specific people, testing with actual users, or comparing metrics on real data.
ticket_completeness	❌	Yes	Title has ≥4 meaningful words (passes criterion a). Description lacks proper context sentences - it reads as problem statement rather than 2+ sentences explaining context (fails criterion b). No acceptance criteria, deliverables, or definition of done is present (fails criterion c). Missing criteria b and c.

create in project Low usage adoption despite high user activity in search and research behaviors 50% transcript_only

User context	Active users on Forward Labs platform who engage in searching and researching daily but show low overall usage metrics
Hypothesis	There may be a disconnect between user activity (search, research) and actual platform usage that needs investigation through user calls and behavior analysis
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, They
Project	546966ce-a9c5-42ac-aa91-974816e14084
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket names a segment ('Active users on Forward Labs platform') but lacks a specific named user or customer. While it identifies a pain point ('low overall usage metrics' and 'disconnect between user activity and actual platform usage'), it does not meet the requirement of naming BOTH a specific user/customer AND a pain point in the way the criterion requires.
hypothesis	✅		The description includes a proposed hypothesis: 'There may be a disconnect between user activity (search, research) and actual platform usage' which suggests a direction for investigation through user calls and behavior analysis.
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks/cycles), priority level (P0/P1/P2), or deadline mentioned. The ticket describes a problem to investigate but lacks concrete temporal constraints or urgency indicators.
test_plan	❌		The ticket mentions 'investigation through user calls and behavior analysis' but does not specify a concrete validation plan with named users, customers, or live data examples. No specific people to contact, PostHog sessions to check, or real data comparisons are referenced.
ticket_completeness	❌	Yes	Missing acceptance criteria, deliverables, or description of what 'done' looks like. Title and description are present, but there's no clear definition of completion.

create in project Users are not adopting the follow-up workflow features despite showing interest in other capabilities like ghostwriter draft and finding people. 65% transcript_only

User context	End users who use the platform for finding people and ghostwriter drafts but have low adoption of follow-up workflows; sales teams using Salesforce and follow-up tools are not utilizing the product's follow-up features.
Hypothesis	Growth can be accelerated by improving communication with users about the follow-up features and understanding their actual follow-up workflows and blockers. Focus product development on reach and track features rather than finding features, as follow-up usage is the main bottleneck.
Deliverable	Customer discovery calls scheduled to understand user follow-up workflows and reasons for non-adoption of follow-up features.
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Forward Labs, Because, Second, Salesforce, Which
Project	84057572-8079-4dea-8a4e-1962063c4c28
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named users/segments identified: 'End users' and 'sales teams using Salesforce'. Specific pain point identified: low adoption of follow-up workflows despite interest in other features, with follow-up usage being the main bottleneck.
hypothesis	✅		The ticket includes a clear hypothesis: 'Growth can be accelerated by improving communication with users about the follow-up features and understanding their actual follow-up workflows and blockers.' It also proposes a direction: 'Focus product development on reach and track features rather than finding features, as follow-up usage is the main bottleneck.'
time_budget	❌	Yes	No explicit time budget (hours/days/weeks/cycles), no priority level (P0/P1/P2), and no deadline specified. The deliverable (customer discovery calls) lacks a concrete completion date.
test_plan	✅		The ticket explicitly mentions 'Customer discovery calls scheduled' as a deliverable, which references real users and involves direct communication to understand actual workflows and blockers. This is a concrete validation plan involving real customers.
ticket_completeness	✅	Yes	Title has 6 meaningful words describing the issue. Description contains 3 sentences providing context about adoption gaps and blockers. Deliverable clearly specifies what done looks like: customer discovery calls to understand workflows and non-adoption reasons.

create in project Need to prioritize and convert logistics automation initiatives into concrete projects with clear scope boundaries 50% transcript_only

User context	Albert Lie at Forward Labs working on end-to-end automation for customer closing, follow-up, and tracking processes
Hypothesis	Focus on 'find and reach' projects first while tabling 'tracking and reach' and 'findings' components to reduce scope and improve execution
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Looks, Forward Labs, Logistics, Etienne Auroux (Linear:e8f6c396-4921-4362-ab74-d6beb0bceada, Slack:U095GPK0YF5)
Project	e0c07324-6699-4cd7-b05d-e0a5465f220f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named user: 'Albert Lie at Forward Labs'. Pain point: need to prioritize and convert logistics automation initiatives into concrete projects with clear scope boundaries, specifically struggling with end-to-end automation for customer closing, follow-up, and tracking processes.
hypothesis	✅		The ticket includes a clear directional statement: 'Focus on 'find and reach' projects first while tabling 'tracking and reach' and 'findings' components to reduce scope and improve execution.' This is a proposed direction for prioritization and scope management.
time_budget	❌	Yes	No explicit time-budget signal, priority level, or deadline present. The ticket mentions prioritization and scope reduction but lacks concrete temporal markers (e.g., '2 hours', 'P1', 'by Friday') that would indicate urgency or time commitment.
test_plan	❌		The ticket mentions Albert Lie at Forward Labs and references customer closing/follow-up processes, but does not include a specific validation plan with concrete steps like testing with real users, checking specific metrics, or validating against actual data. It focuses on scope prioritization rather than validation methodology.
ticket_completeness	❌	Yes	Title meets criteria (a) with 7 meaningful words. Description has 2 sentences meeting criteria (b). However, criteria (c) fails - there are no explicit acceptance criteria, deliverables, or clear definition of 'done'. The ticket describes what is being worked on and prioritization decisions but lacks concrete success metrics or completion criteria.

create in project Unclear definition of what 'progress' means for the product roadmap across different timeframes (2 weeks vs 1 month) 50% transcript_only

Hypothesis	Progress should be defined as getting usage or activating all users
Time budget	2 weeks to 1 month
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Because
Project	e0c07324-6699-4cd7-b05d-e0a5465f220f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket lacks a named user, customer segment, or specific persona. While it mentions 'all users', this is generic and not a named segment. The description addresses a process/definition problem (unclear definition of 'progress') rather than a specific pain point experienced by identifiable users.
hypothesis	✅		The description includes a proposed direction: 'Progress should be defined as getting usage or activating all users' which clearly states what the solution/hypothesis is for defining progress.
time_budget	✅	Yes	Ticket explicitly states budget of '2 weeks to 1 month' in the Budget field, which is a clear time-budget signal.
test_plan	❌		The ticket contains no validation plan referencing real users, customers, or live data. It only states what progress 'should be defined as' without any concrete testing approach like user outreach, data comparison, or live environment checks.
ticket_completeness	❌	Yes	Missing acceptance criteria or clear definition of 'done'. The description lacks context sentences explaining the problem/impact, and there's no explicit acceptance criterion, deliverable, or definition of what successful completion looks like.

create in project Unclear whether the product's value proposition actually helps existing users close customers, not just find them 65% transcript_only

User context	Existing (old) users who find customers but struggle with follow-up and closing
Hypothesis	Adding follow-up/closing support to the finding-customers feature will improve the value proposition and customer outcomes
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Probably, Because
Project	42d123ac-e72f-44c1-bece-787c63ff348f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named segment: 'Existing (old) users who find customers'. Specific pain point: 'struggle with follow-up and closing'. Both elements are present.
hypothesis	✅		The description includes a clear proposed direction: 'Adding follow-up/closing support to the finding-customers feature will improve the value proposition and customer outcomes.' This is a hypothesis statement about the proposed solution.
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks/cycles), no priority level (P0/P1/P2), and no clear deadline or deliverable specified. The ticket describes a problem and potential solution but lacks concrete scheduling or urgency markers.
test_plan	❌		The ticket describes a problem and proposed solution but contains no concrete validation plan referencing real users, customers, or live data. There are no specific names, PostHog checks, customer interviews, or comparative testing mentioned.
ticket_completeness	❌	Yes	Title has ≥4 meaningful words ✓. Description has ≥2 sentences ✓. However, no acceptance criteria, deliverables, or definition of 'done' is present—the description states what might help but doesn't specify what actually needs to be built or how to measure completion.

create in project Need to validate that the core value proposition is real by establishing clear metrics for product adoption and customer success 75% transcript_only

User context	Forward Labs (Albert Lie) and team - users need to prove value through customer usage patterns (copy draft, edit draft, sending draft) and customer acquisition results (status customers closing deals)
Hypothesis	Value prop can be proven through three sequential metrics: (1) get more people to try and track the product, (2) make it useful by fixing broken features related to tracking and reach, (3) demonstrate measurable results in customer closure rates
Deliverable	Metrics framework and focus areas for product fixes tied to tracking and reach functionality
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Because, Forward Labs, You, Number, Try, Yep, Keypad
Project	42d123ac-e72f-44c1-bece-787c63ff348f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named user/segment: 'Forward Labs (Albert Lie) and team' + 'status customers'. Pain point: users need to prove value through usage patterns and acquisition results; broken features related to tracking and reach prevent demonstrating measurable results in customer closure rates.
hypothesis	✅		The ticket includes a clear proposed direction/hypothesis: the value proposition can be proven through three sequential metrics involving user adoption, feature fixes, and customer closure rates. This is a specific 'we think the solution is X' statement outlining the approach to validate the core value proposition.
time_budget	❌	Yes	No explicit time budget (hours/days/weeks), no priority level (P0-P2), and no deadline specified. While there is a clear deliverable (metrics framework), without temporal constraints it cannot be assessed as having urgency signals.
test_plan	✅		References real users (Forward Labs, Albert Lie) and specific customer success metrics (copy draft, edit draft, sending draft actions; customer acquisition results; deal closure rates). Includes plan to validate with actual customer usage patterns and business outcomes.
ticket_completeness	✅	Yes	Title has 13 meaningful words exceeding 4-word threshold. Description contains 3 sentences providing context about Forward Labs, user needs, and sequential metrics. Deliverable explicitly states 'Metrics framework and focus areas for product fixes' clearly defining what done looks like.

create in project Managing user requests that appear simple but require complex multi-layered solutions (e.g., end-to-end campaign automation), and systematically activating new users rather than relying on random polling 65% transcript_only

User context	New users and existing users requesting features like end-to-end automation for campaigns; currently being reached through ad-hoc polling methods
Hypothesis	Implement a systematic approach to user activation that includes multiple channels (calling, email campaigns, and other tactics) rather than random outreach; couple this with a process to fix issues discovered through user engagement
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Because, Which
Project	5143b16d-1e33-4a23-9245-82cb5900b5a9
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket identifies a segment ('new users and existing users') but lacks a specific named user or customer. While it mentions a pain point ('requests that appear simple but require complex multi-layered solutions'), the description focuses more on process/activation methodology than on a concrete pain point users experience. The pain point is vague and process-oriented rather than specific to user experience.
hypothesis	❌		The description outlines the problem and desired outcome (systematic user activation with multiple channels) but does not include a specific proposed direction, hypothesis, or 'we think the solution is X' statement. It describes what should be done but not how or what the team believes will work.
time_budget	❌	Yes	No explicit time budget (hours/days/weeks/cycles), no priority level (P0/P1/P2), and no clear deadline. The ticket describes a general initiative/strategy rather than a bounded deliverable with urgency signals.
test_plan	❌		The ticket describes a systematic approach to user activation and engagement but contains no specific validation plan referencing real users, customers, or live data. There are no concrete examples like 'contact Brian to test automation flow', 'measure activation rates on cohort X', or 'validate with 10 existing customers before launch'. The mention of 'user engagement' is too vague and lacks actionable validation details.
ticket_completeness	✅	Yes	Title has 18 meaningful words describing complex user request management. Description has 2+ sentences providing context about ad-hoc polling and need for systematic activation. Multiple acceptance criteria implied: systematic approach with multiple channels (calling, email), process to fix discovered issues, and end-to-end campaign automation support.

create in project New team members (like Luis) lack clarity on tasks, ownership, and escalation paths when onboarded, causing confusion and bottlenecks in execution. 75% transcript_only

User context	Luis (new team member arriving Monday) - doesn't understand task requirements, doesn't know who to contact for help, and doesn't know who owns problem resolution.
Hypothesis	Schedule pre-arranged calls/check-ins for new team members on their first day so they have structured guidance and clear points of contact rather than figuring it out ad-hoc.
Time budget	Monday (implied immediate/next cycle)
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Imagine, Louise Dungca (Linear:457821c6-bea0-49ae-8bf8-3bc892bf7c12, Slack:U07GYNH7JS2), After, Then, Before
Project	e0c07324-6699-4cd7-b05d-e0a5465f220f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	The ticket includes both a named user ('Luis', a new team member) and specific pain points he experiences (lacks clarity on task requirements, doesn't know who to contact for help, doesn't know who owns problem resolution).
hypothesis	✅		The ticket includes a proposed direction: 'Schedule pre-arranged calls/check-ins for new team members on their first day so they have structured guidance and clear points of contact rather than figuring it out ad-hoc.' This is a clear 'we think the solution is X' statement.
time_budget	✅	Yes	Explicit time-budget signal present: 'Monday (implied immediate/next cycle)' indicates immediate urgency with a clear deadline for onboarding Luis. This is a next-cycle/this-week priority item.
test_plan	✅		The ticket explicitly references a real user (Luis, arriving Monday) and implies validation through scheduled check-ins with him as the test subject for the onboarding process. This is a concrete plan to validate with an actual new team member rather than generic testing.
ticket_completeness	✅	Yes	Title has 14+ meaningful words describing the problem. Description provides 2+ sentences of context about Luis's specific pain points. Acceptance criteria implied through the solution: pre-arranged calls/check-ins on first day with structured guidance and clear points of contact establish what 'done' looks like.

create in project How to efficiently book user calls for customer discovery when the team is still in training and building processes can't be completed within the current month. 65% transcript_only

User context	Internal team members (Sarah, Luis) being trained on customer calling/outreach processes; broader user activation effort involving calls, email, and product marketing.
Hypothesis	Consider booking calls through an external or alternative mechanism rather than relying solely on newly trained internal team members, since training them is an epic-level effort extending beyond April.
Time budget	April (current month constraint mentioned)
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Then, Cyril Cero (Linear:c64fc65d-d365-40e3-8eef-64c1d12ba53c, Slack:U07JJM0PNA1), Louise Dungca (Linear:457821c6-bea0-49ae-8bf8-3bc892bf7c12, Slack:U07GYNH7JS2)
Project	e89d292d-0ded-4b20-95e0-689014891be6
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket names specific users (Sarah, Luis) and mentions a pain point (training taking too long, processes can't be completed within the month), but the pain point is about internal process/training delays rather than a customer or end-user experiencing a specific problem with the product or service. The ticket lacks a named customer segment and their experienced pain point.
hypothesis	✅		The ticket includes a proposed direction: 'Consider booking calls through an external or alternative mechanism rather than relying solely on newly trained internal team members.' This is a clear hypothesis about the solution.
time_budget	✅	Yes	Contains explicit time-budget signal: 'current month' (April) constraint and acknowledgment that work extends 'beyond April', indicating a multi-week/multi-cycle scope. Also implies priority through the word 'epic-level effort' suggesting significant complexity and urgency around customer discovery timing.
test_plan	✅		The ticket references real team members (Sarah, Luis) and mentions validation through actual customer calls as part of the user activation effort. It specifies reaching out to real users for discovery calls, which constitutes validation with real users rather than generic testing.
ticket_completeness	❌	Yes	Missing acceptance criteria or clear definition of 'done'. The title and description meet their requirements, but there are no explicit acceptance criteria, deliverables, or bullets describing what completion looks like (e.g., 'calls booked by X date', 'alternative mechanism identified', 'process documented').

create unclassified Unclear value proposition for listeners joining calls that the organizer is already participating in 50% transcript_only

User context	Shan Wu and Albert Lie discussing a follow-up/listening feature where people can join calls after the fact
Hypothesis	The feature allows asynchronous call joining and feedback collection, but the actual learning value for joiners beyond the original participant is questionable
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Then
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named users present (Shan Wu and Albert Lie) and specific pain point identified (unclear value proposition/learning value for listeners joining calls asynchronously).
hypothesis	✅		The description includes a hypothesis/concern statement: 'the actual learning value for joiners beyond the original participant is questionable' - this identifies a proposed problem with the solution's value proposition.
time_budget	❌	Yes	No explicit time-budget signal, priority level, or deadline mentioned. The ticket describes a feature discussion without temporal constraints or urgency markers.
test_plan	❌		The ticket mentions discussions with Shan Wu and Albert Lie but does not include a specific validation plan referencing real users, customers, or live data testing. No concrete actions like 'reach out to X to test', checking metrics, or comparing outputs are specified.
ticket_completeness	❌	Yes	Missing acceptance criteria or definition of 'done'. Title and description meet requirements, but no acceptance criteria, deliverables, or bullets describing what completion looks like.

create in project Team lacks user discovery and hypothesis-formation skills, creating a tradeoff between maximizing user activation/problem-fixing and investing in team training 75% transcript_only

User context	Albert Lie's team members who recently joined user research calls need to learn how to form hypotheses, prioritize questions before calls, and evaluate problem workability post-call. The team is new to user discovery.
Hypothesis	The team should choose between two competing goals: (1) maximizing user activations and fixes now with experienced operators, or (2) training the team in discovery skills with lower near-term output but long-term capability building.
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, There, Number, Because, Even, Basically, Activating, User, They
Project	e8ae7471-ee8f-44df-be2c-5971120a3440
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named user: 'Albert Lie's team members' (a specific team). Pain point: they 'need to learn how to form hypotheses, prioritize questions before calls, and evaluate problem workability post-call' and the team faces a tradeoff between immediate user activation/problem-fixing versus investing in discovery skill training. Both elements are present.
hypothesis	❌		The ticket describes a problem and a tradeoff between two competing goals, but does not include a specific proposed direction, hypothesis, or 'we think the solution is X' statement. It presents the dilemma without indicating which direction the team should take or what they hypothesize will be the best path forward.
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks/cycles), no priority level (P0/P1/P2), and no clear deadline. The ticket describes a strategic tradeoff but lacks concrete temporal or urgency constraints needed for estimation and scheduling.
test_plan	❌		The ticket describes a strategic decision between two competing priorities but contains no validation plan. There are no references to specific users, customers, live data, or concrete testing activities (e.g., 'have team shadow Albert on 3 calls', 'measure hypothesis quality on next 5 customer interviews', 'compare discovery output before/after training'). It is a planning/decision ticket, not an execution ticket with a validation approach.
ticket_completeness	❌	Yes	Missing acceptance criteria. The ticket has a strong title (≥4 meaningful words) and a description with 2+ sentences providing context, but lacks any explicit acceptance criteria, deliverables, or definition of 'done' to measure completion.

create in project Need to systematically increase participation and get more people on calls as part of activation efforts 55% transcript_only

User context	Albert Lie and Shan Wu (Forward Labs leadership) need to drive engagement; broader team members should join when available
Hypothesis	Albert and Shan should own activation/getting people on calls without waiting for full team availability; team joins if available
Time budget	Later today for deeper discussion
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Activation, Therefore, Yep, Then
Project	546966ce-a9c5-42ac-aa91-974816e14084
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket names specific users (Albert Lie, Shan Wu, Forward Labs leadership) but lacks a clearly articulated specific pain point. It describes a desired action (increase participation/engagement) rather than a concrete problem they experience.
hypothesis	❌		The ticket describes goals and ownership assignments but does not include a proposed direction, hypothesis, or 'we think the solution is X' statement about how to achieve the increased participation.
time_budget	✅	Yes	Contains explicit time-budget signal: 'Later today for deeper discussion' indicates same-day urgency and implies this is a high-priority activation effort requiring immediate attention.
test_plan	❌		The ticket describes engagement and activation goals but contains no specific validation plan referencing real users, customers, live data, or concrete testing scenarios. It lacks details like 'test with X customer', 'measure Y metric in Z system', or 'validate with specific person'. Generic statements about team participation do not constitute a validation plan.
ticket_completeness	❌	Yes	Missing acceptance criteria or clear definition of 'done'. Title has ≥4 meaningful words and description has ≥2 sentences of context, but no explicit acceptance criteria, deliverables, or metrics defining what success looks like.

create in project Lack of clear project definition and ownership assignment is causing weekly confusion about what work to prioritize and execute 72% transcript_only

User context	The team (including Hakeem, Sarah, and others) doesn't have clarity on which projects they own or should work on, leading to inefficient allocation and unowned bugs
Hypothesis	Defining projects and owners more clearly upfront will eliminate weekly deliberation about priorities and enable straightforward task matching between projects and people
Time budget	Today (define problems and owners clearly in this meeting and car ride)
Deliverable	Clear mapping of projects to owners and clarification of responsibility assignment
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Hmm, Because, Yep, Number, Hakiem Aulia (Linear:1ca29403-c25e-4b6e-b952-47881d3ce0d2, Slack:U06T1PFJHKQ), Etienne Auroux (Linear:e8f6c396-4921-4362-ab74-d6beb0bceada, Slack:U095GPK0YF5), Cyril Cero (Linear:c64fc65d-d365-40e3-8eef-64c1d12ba53c, Slack:U07JJM0PNA1), Hakim, Email, Automation, They, There
Project	e0c07324-6699-4cd7-b05d-e0a5465f220f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Includes named users (Hakeem, Sarah, and others) and specific pain point (weekly confusion about work prioritization, inefficient allocation, unowned bugs)
hypothesis	✅		The description includes a clear hypothesis: 'Defining projects and owners more clearly upfront will eliminate weekly deliberation about priorities and enable straightforward task matching between projects and people.' This is a proposed direction statement explaining what the team thinks the solution is.
time_budget	✅	Yes	Contains explicit time-budget signal: 'Today' with specific scope (define problems and owners in meeting/car ride). Clear deliverable: project-to-owner mapping and responsibility clarification.
test_plan	❌		The ticket describes an organizational/process problem and deliverable (project-to-owner mapping) but contains no validation plan that references real users, customers, or live data. There is no mention of reaching out to specific team members to validate the solution, checking actual work allocation post-implementation, or comparing outcomes before/after the clarification effort.
ticket_completeness	✅	Yes	Title has 13 meaningful words exceeding the 4-word minimum. Description contains 2+ sentences providing context about team confusion and the benefit of clarity. Deliverable explicitly states 'Clear mapping of projects to owners and clarification of responsibility assignment' which defines what done looks like.

create in project Uncertainty about whether the email scanning infrastructure is performing adequately in terms of quality, speed, and coverage. 60% transcript_only

User context	Forward Labs product users who rely on auto-import functionality powered by email scanning.
Hypothesis	The email scanning infrastructure may need evaluation across three dimensions: scanning quality, scanning speed, and scanning coverage.
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs
Project	b70abc4b-a6c1-4031-8293-eeedeb91629e
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named segment: 'Forward Labs product users who rely on auto-import functionality'. Pain point: uncertainty about email scanning infrastructure performance across quality, speed, and coverage dimensions.
hypothesis	❌		The description identifies dimensions that need evaluation but does not propose a direction, hypothesis, or potential solution. It states a problem and areas for investigation without suggesting what the solution might be.
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks/cycles), no priority level (P0/P1/P2), and no clear deadline. The ticket describes a problem area requiring evaluation but lacks concrete urgency indicators or deliverable deadlines.
test_plan	❌		The ticket identifies a problem area (email scanning infrastructure evaluation) but contains no specific validation plan referencing real users, customers, or live data. It mentions 'Forward Labs product users' generically but provides no concrete examples like 'contact [name] to test', specific PostHog metrics to check, or comparisons on real datasets.
ticket_completeness	❌	Yes	Title lacks clarity and reads like a problem statement rather than an actionable work item. Description has only 2 sentences but lacks concrete context about the issue. No acceptance criteria, deliverables, or definition of done provided.

create unclassified Balancing skill development on weaknesses versus leveraging existing strengths when allocating people to projects 60% transcript_only

User context	Shan Wu and team members at Forward Labs who need to decide how to invest in people's growth while maintaining project effectiveness
Hypothesis	People should primarily focus on their strengths while having controlled opportunities to work on weaknesses, rather than being stretched across both simultaneously
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Because
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named user/segment: 'Shan Wu and team members at Forward Labs'. Specific pain point: deciding how to balance skill development on weaknesses versus leveraging existing strengths when allocating people to projects, with the tension between growth investment and project effectiveness.
hypothesis	✅		The description includes a clear proposed direction/hypothesis: 'People should primarily focus on their strengths while having controlled opportunities to work on weaknesses, rather than being stretched across both simultaneously.' This is a specific stance on how to balance skill development.
time_budget	❌	Yes	No explicit time budget (hours/days/weeks), no priority level (P0/P1/P2), and no clear deadline. This appears to be a strategic discussion topic rather than a time-bound actionable ticket.
test_plan	❌		This ticket describes a general people management strategy/principle rather than a software feature or project with specific deliverables. It contains no validation plan, no mention of real users to test with, no live data to compare, and no concrete acceptance criteria that could be validated. It reads as a discussion topic or decision framework, not an actionable ticket with measurable validation steps.
ticket_completeness	❌	Yes	Missing acceptance criteria/deliverables. Title has ≥4 meaningful words and description has ≥2 sentences of context, but there is no definition of what 'done' looks like - no acceptance criteria, specific deliverables, or concrete outcomes listed.

create in project Need to enforce consistent UI reviews across Track & Reach product to leverage Louie's UX expertise 55% transcript_only

User context	Product team (Louie with UX/user understanding strength, Hakeem with technical depth) working on Track & Reach features
Hypothesis	Systematically enforce UI reviews led by Louie across the Track & Reach track to ensure UX consistency and quality
Deliverable	UI review process enforcement across Track & Reach
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Louie, Louise Dungca (Linear:457821c6-bea0-49ae-8bf8-3bc892bf7c12, Slack:U07GYNH7JS2), Track, Reach, Hakiem Aulia (Linear:1ca29403-c25e-4b6e-b952-47881d3ce0d2, Slack:U06T1PFJHKQ)
Project	d8c139a7-ab1f-4c87-86a0-ef187085917a
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket names individuals (Louie, Hakeem) and a team (Product team) but does not identify a named user, customer, or segment experiencing a problem. It describes an internal process improvement rather than a specific pain point experienced by users or customers.
hypothesis	❌		The ticket describes what needs to be done (enforce UI reviews) and who should do it (Louie), but does not include a sentence or bullet proposing a specific direction, hypothesis, or solution for how to enforce the reviews or what the underlying problem is that this solves.
time_budget	❌	Yes	No explicit time budget (hours/days/weeks), no priority level (P0-P2), and no deadline specified. While there is a deliverable mentioned (UI review process enforcement), it lacks a concrete deadline to make it actionable.
test_plan	❌		The ticket describes a process improvement (enforcing UI reviews) but contains no validation plan that references real users, customers, or live data. There is no mention of testing with actual users, checking real user sessions, comparing outputs on real leads, or any concrete validation mechanism involving real-world scenarios.
ticket_completeness	✅	Yes	Title has 11 meaningful words exceeding the 4-word minimum. Description contains 2 sentences providing context about the product team and their roles. Deliverable is explicitly stated: 'UI review process enforcement across Track & Reach' which clearly defines what 'done' looks like.

create unclassified Unclear process for handling UI review handoffs and skill gaps when team members like Luis take over specific tasks in a workflow. 50% transcript_only

User context	Luis (UI reviewer) and the team working on a review-edit-send workflow process; Shan Wu is uncertain about how to structure task handoffs when skill gaps exist.
Hypothesis	Implement a configurable review process that can mandate specific reviewers (e.g., Luis for UI) and establish clear handoff procedures between team members, potentially through user config and automation settings.
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Louise Dungca (Linear:457821c6-bea0-49ae-8bf8-3bc892bf7c12, Slack:U07GYNH7JS2), You, Because, Who, List
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named users identified: Luis (UI reviewer) and Shan Wu. Specific pain point identified: uncertainty about structuring task handoffs when skill gaps exist, and unclear process for handling UI review handoffs. Both criteria met.
hypothesis	✅		The description includes a proposed direction: 'Implement a configurable review process that can mandate specific reviewers (e.g., Luis for UI) and establish clear handoff procedures between team members, potentially through user config and automation settings.' This is a clear 'we think the solution is X' statement.
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks/cycles), no priority level (P0/P1/P2), and no clear deadline mentioned. The ticket describes a problem and proposes a solution but lacks concrete urgency or scope indicators.
test_plan	✅		The ticket references real users (Luis as UI reviewer, Shan Wu) and a real workflow (review-edit-send process), indicating validation would involve these actual team members testing the handoff and configuration procedures.
ticket_completeness	✅	Yes	Title has 11 meaningful words describing a specific process problem. Description contains 2 sentences providing context about the team situation and skill gaps. Implementation section describes what done looks like: a configurable review process with specific reviewer mandates and clear handoff procedures.

create in project Difficulty in determining accurate metrics (click rate vs open rate) for deciding what content to show users 55% transcript_only

User context	End users receiving content, with metrics being evaluated for relevance and engagement
Hypothesis	Neither click rate nor open rate alone provides accurate signals for content decisions; metrics may be inherently non-deterministic for this use case
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Open, There, Because, Etienne Auroux (Linear:e8f6c396-4921-4362-ab74-d6beb0bceada, Slack:U095GPK0YF5)
Project	871a9ee3-a8c7-4a92-9806-eeb57428edd8
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket identifies a pain point (difficulty determining accurate metrics for content decisions) but lacks a named user, customer, or segment. 'End users' is too generic and doesn't meet the requirement for a specifically named entity.
hypothesis	❌		The description identifies the problem and states that neither metric alone works, but does not propose a specific direction or hypothesis for solving it. It concludes the metrics may be non-deterministic rather than suggesting a solution approach.
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks/cycles), no priority level (P0/P1/P2), and no clear deadline specified. The ticket describes a problem but lacks concrete scheduling or urgency indicators.
test_plan	❌		The ticket describes a problem but contains no validation plan that references real users, customers, or live data. There are no mentions of reaching out to specific people, checking actual user sessions, or testing with real content/leads.
ticket_completeness	❌	Yes	Title has ≥4 meaningful words ✓, description has ≥2 sentences ✓, but no acceptance criteria, deliverables, or definition of 'done' is present ✗

create unclassified Team members (Louise and Saito) are overworked and stressed, creating a workload balancing issue. 55% transcript_only

User context	Louise and Saito are experiencing stress and overwork; Shan Wu is concerned about their wellbeing and mentions hearing about Louise's stress from Saito during one-on-ones.
Hypothesis	Consider distributing work to other team members (Farrell, Hakeem, or Kim) instead of further burdening Louise and Saito; actively help them reduce their workload.
Time budget	P2 priority
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Forward Labs, Farrell, Hakiem Aulia (Linear:1ca29403-c25e-4b6e-b952-47881d3ce0d2, Slack:U06T1PFJHKQ), Kim, Because Saito, Louise Dungca (Linear:457821c6-bea0-49ae-8bf8-3bc892bf7c12, Slack:U07GYNH7JS2), Saito, engineer@breadd.ai (Linear:773e5d48-dbef-487f-9cd3-c3d3320c6bd7), Etienne Auroux (Linear:e8f6c396-4921-4362-ab74-d6beb0bceada, Slack:U095GPK0YF5), Find, Still
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named users identified: Louise and Saito. Specific pain point identified: stress and overwork/workload imbalance. Both criteria (a) and (b) are met.
hypothesis	✅		The description includes a proposed direction: 'Consider distributing work to other team members (Farrell, Hakeem, or Kim) instead of further burdening Louise and Saito; actively help them reduce their workload.' This is a clear hypothesis about the solution.
time_budget	✅	Yes	Contains explicit priority signal 'P2' which implies urgency and relative size/scope. P2 priority indicates this is a meaningful issue requiring timely action, though not critical emergency level.
test_plan	❌		The ticket describes a workload balancing issue but contains no validation plan. It mentions real people (Louise, Saito, Shan Wu, Farrell, Hakeem, Kim) but does not reference any specific testing, measurement, or validation approach such as checking workload metrics post-redistribution, conducting follow-up 1-on-1s to confirm stress reduction, or comparing task completion rates before/after the change.
ticket_completeness	✅	Yes	Title has 11 meaningful words exceeding the 4-word minimum. Description contains 2+ sentences providing context about the stress situation and team members involved. Acceptance criteria are present: distribute work to other team members (Farrell, Hakeem, Kim) and actively help reduce Louise and Saito's workload, defining what 'done' looks like.

create in project Unclear ownership and assignment of critical infrastructure work across categories (Find Contact, Acquire, Onboard, Retain) 50% transcript_only

User context	Team members including Shan Wu, Albert Lie, Louise, and Hakim need clarity on who owns different functional areas - particularly for infrastructure and long-term initiatives with KPIs
Hypothesis	Assign Find Contact (critical infrastructure) to Hakim or external contact, Acquire to Shan Wu full-time, Onboard training to Louise, and Retain (support/results) as part of overall strategy
Time budget	Long-term with potential triggers from deals (D2 or later)
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Good, Hakim, Because, Acquire, Louise Dungca (Linear:457821c6-bea0-49ae-8bf8-3bc892bf7c12, Slack:U07GYNH7JS2), Retain
Project	e0c07324-6699-4cd7-b05d-e0a5465f220f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	While the ticket names specific users (Shan Wu, Albert Lie, Louise, Hakim), it does not describe a specific pain point they experience. Instead, it describes an organizational problem (unclear ownership) and proposes a solution (assignment of roles). No customer-facing pain point or user problem is articulated.
hypothesis	✅		The description includes clear proposed solutions: 'Assign Find Contact (critical infrastructure) to Hakim or external contact, Acquire to Shan Wu full-time, Onboard training to Louise, and Retain (support/results) as part of overall strategy' - these are explicit 'we think the solution is X' statements for ownership assignments.
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks/cycles), no priority label (P0/P1/P2), and no clear deadline. 'Long-term' is vague and 'potential triggers from deals' is conditional, not a definitive schedule.
test_plan	❌		The ticket describes organizational assignments and ownership clarification but contains no validation plan referencing real users, customers, or live data. It does not mention testing with actual people, checking real user data, or validating changes against concrete examples.
ticket_completeness	✅	Yes	Title has 9 meaningful words exceeding 4-word threshold. Description provides 2 sentences of context explaining the clarity need and team members involved. Acceptance criteria are present: specific assignments for Find Contact (Hakim/external), Acquire (Shan Wu full-time), Onboard (Louise), and Retain (overall strategy), with budget/trigger guidance. All three requirements met.

create in project Unclear resource allocation and support needs for the campaign project that Ethan is currently building alone 55% transcript_only

User context	Ethan, who is working solo on a large campaign project at Forward Labs; the team needs to understand retention strategy across different KPIs and billing metrics
Hypothesis	Ethan may need additional help to deliver the campaign project effectively, but the decision is pending clarification on project scope and priorities
Time budget	next week
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Because, Learn, There, Shira, All, Then, Ethan
Project	871a9ee3-a8c7-4a92-9806-eeb57428edd8
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named user: Ethan. Specific pain point: working solo on a large campaign project and unclear resource allocation/support needs, with pending clarification on project scope and priorities needed to understand retention strategy across KPIs and billing metrics.
hypothesis	❌		The ticket describes the problem (unclear resource allocation, Ethan working solo) and mentions a potential need (additional help), but does not include a specific proposed direction, hypothesis, or 'we think the solution is X' statement. The decision on help is explicitly stated as 'pending clarification' rather than proposing a direction.
time_budget	✅	Yes	Contains explicit time-budget signal: 'next week' indicates urgency and scope constraint
test_plan	❌		The ticket describes a resource allocation and support problem but contains no validation plan referencing real users, customers, or live data. There are no specific testing instructions like contacting Ethan, checking actual metrics, or validating with real campaign data.
ticket_completeness	❌	Yes	Title has ≥4 meaningful words ✓, Description has ≥2 sentences ✓, but lacks any acceptance criteria, deliverables, or definition of 'done' ✗

create in project Team members are not conducting real user testing for IterationV0 because it is difficult to schedule sessions and people lack training on how to execute tests. 72% transcript_only

User context	Product team members responsible for testing IterationV0 features; they struggle with booking user sessions, forget to conduct tests, are busy with other priorities, and don't know the testing process.
Hypothesis	Provide quick onboarding sessions to team members about the feature, help them formulate testing questions collaboratively, and offer hands-on support from Albert or Shan to guide them through the testing process while keeping ownership with the team.
Time budget	ETM expected to ship follow-up playbook setting this week; testing iteration to follow
Deliverable	Onboarding sessions for team members on how to conduct real user tests for IterationV0, with question formulation support
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Maybe Hakim, Reach, Iteration, Let, Hard, Then
Project	d8c139a7-ab1f-4c87-86a0-ef187085917a
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	Includes a named segment (product team members) but the pain points listed (difficulty scheduling, lack of training, busy with other priorities, don't know the process) are about internal process/capability gaps rather than a specific pain point experienced by actual users or customers. The ticket is about internal testing execution challenges, not a user/customer pain point.
hypothesis	✅		The description includes a clear proposed direction: 'Provide quick onboarding sessions to team members about the feature, help them formulate testing questions collaboratively, and offer hands-on support from Albert or Shan to guide them through the testing process while keeping ownership with the team.' This is a specific 'we think the solution is X' statement that proposes how to address the scheduling and training barriers.
time_budget	✅	Yes	Contains explicit deadline 'this week' for ETM playbook and clear deliverable (onboarding sessions for user testing). The sequential dependency ('testing iteration to follow') implies urgency and a defined scope.
test_plan	❌		The ticket describes a process improvement for conducting testing but does not reference any specific real user, customer, or live data to validate against. It mentions 'team members' and 'Albert or Shan' providing support, but does not specify actual users to test with, customer names, specific PostHog metrics, or concrete data comparisons. The deliverable is training on how to test, not a validation plan with named participants or data sources.
ticket_completeness	✅	Yes	Title has 5+ meaningful words describing the problem. Description contains 2+ sentences providing context about team struggles and proposed solutions. Deliverable clearly defines what 'done' looks like: onboarding sessions with question formulation support.

create in project The 'send' experience has multiple reliability and formatting issues that undermine user trust in the system 50% transcript_only

User context	Users relying on the send functionality need to trust that messages are delivered correctly with proper signatures, formatting, and recipient routing
Hypothesis	Systematically address identified failure modes: VR log reliability, signature correctness, thread copying format, test sending capability, email formatting, and recipient delivery accuracy
Time budget	P3
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Because, Trust, Send, One, Two, Three, Those, Reliable
Project	84057572-8079-4dea-8a4e-1962063c4c28
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket identifies a generic user segment ('Users relying on the send functionality') and multiple pain points (reliability, formatting, signatures, routing), but lacks a named user, specific customer, or well-defined segment. The description is about 'send functionality' broadly rather than a specific user persona or use case.
hypothesis	❌		The description lists problems to address ('identified failure modes') but does not include a proposed direction, hypothesis, or suggested solution for how to fix these issues. It states what needs to be fixed, not how or what the team thinks the solution should be.
time_budget	❌	Yes	P3 is a priority level but does not imply urgency or time budget. No explicit time duration (hours/days/weeks) or deadline is stated. The ticket lacks a clear time-budget signal.
test_plan	❌		The ticket describes multiple issues and asks to 'systematically address identified failure modes' but contains no specific validation plan that references real users, customers, or live data. No mention of reaching out to specific people, testing with real accounts, or comparing actual output before/after. Generic problem statement without concrete validation steps.
ticket_completeness	❌	Yes	Title passes (6 meaningful words). Description has 2 sentences but lacks specific context about actual issues. Missing explicit acceptance criteria, deliverables, or clear 'done' definition—only lists vague failure modes without measurable completion criteria.

create in project Unable to reliably measure and ensure quality of targeted email outreach messages, making it difficult to gauge whether playbooks are effective across different users and shippers. 70% transcript_only

User context	Shan Wu and the Forward Labs team building email campaign tools; specifically affects users trying to send personalized outreach and campaign managers evaluating message quality across different target segments.
Hypothesis	Quality can be defined and measured by criteria such as: sounding personal and handwritten, appearing authentic (not AI-generated or automated), showing homework was done, being credible and relevant, and most importantly being specific, concrete, and real with detailed mentions rather than generic content.
Time budget	P0 priority
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Yep, Nice, Shipping, Target, See, Sackman, Still, There, Etienne Auroux (Linear:e8f6c396-4921-4362-ab74-d6beb0bceada, Slack:U095GPK0YF5), Words
Project	871a9ee3-a8c7-4a92-9806-eeb57428edd8
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named users/segments present: 'Shan Wu and the Forward Labs team', 'users trying to send personalized outreach', 'campaign managers', and 'different target segments'. Specific pain point present: unable to reliably measure and ensure quality of targeted email messages, difficulty gauging playbook effectiveness, and messages containing generic content rather than specific/concrete details.
hypothesis	❌		The ticket defines quality criteria and the problem, but does not include a proposed direction, hypothesis, or suggested solution for how to measure or ensure quality.
time_budget	✅	Yes	Ticket contains explicit P0 priority designation, which signals high urgency and implies this is a critical, time-sensitive item requiring immediate attention.
test_plan	❌		The ticket defines quality criteria and identifies affected users (Shan Wu, Forward Labs team, campaign managers) but does not include a specific validation plan that references real users for testing, live data comparison, or post-ship measurement. No concrete steps like 'test with X users' or 'compare outputs on real campaigns' are mentioned.
ticket_completeness	✅	Yes	Title has 7+ meaningful words describing the problem. Description provides 2+ sentences of context about affected users and teams. Quality criteria (personal/authentic/homework/credible/specific) serve as acceptance criteria defining what 'done' looks like.

create in project Need to establish a testing process for trust-message reviews with a test client 65% transcript_only

User context	Etienne (creator of the feature) needs help testing trust-message reviews; Albert Lie and Shan Wu are available to assist
Hypothesis	Add a test client to the playbook to enable trust-message review testing
Time budget	Before Shan Wu's departure on Wednesday
Deliverable	Test client added to playbook for trust-message reviews
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Etienne Auroux (Linear:e8f6c396-4921-4362-ab74-d6beb0bceada, Slack:U095GPK0YF5), engineer@breadd.ai (Linear:773e5d48-dbef-487f-9cd3-c3d3320c6bd7), Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7)
Project	84057572-8079-4dea-8a4e-1962063c4c28
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket names users (Etienne, Albert Lie, Shan Wu) but does not identify a named customer/segment experiencing a pain point. Instead, it describes an internal testing need rather than a customer pain point.
hypothesis	❌		The ticket describes what needs to be done (add a test client to the playbook) but does not include a sentence or bullet describing a proposed direction, hypothesis, or 'we think the solution is X' statement. It states the deliverable but not the reasoning or hypothesis behind it.
time_budget	✅	Yes	Clear deadline: 'Before Shan Wu's departure on Wednesday' provides explicit time constraint. Specific deliverable identified: 'Test client added to playbook for trust-message reviews'. This establishes both urgency and scope.
test_plan	✅		The ticket references real people (Etienne, Albert Lie, Shan Wu) who will conduct testing, and mentions a specific deadline (before Shan Wu's departure Wednesday), indicating concrete user validation rather than generic testing.
ticket_completeness	✅	Yes	Title has 7 meaningful words (≥4), description contains 2+ sentences of context, and there is a clear deliverable: 'Test client added to playbook for trust-message reviews'

create in project Need to validate quality of trust messages generated by the new user-instructed playbook before full release 55% transcript_only

User context	Shan Wu and team need to manually review trust message quality from the test client to ensure acceptable quality standards before shipping
Hypothesis	Include trust message generation capability in test client this cycle to enable manual quality review; delay one of two planned trust messages to manage quality validation workload
Time budget	This cycle
Deliverable	Test client with trust message generation capability for manual quality review
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Can, Here, Your, Review, Test, Emma, Get
Project	84057572-8079-4dea-8a4e-1962063c4c28
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named user 'Shan Wu and team' is identified, and the specific pain point is 'need to manually review trust message quality' before release to ensure acceptable quality standards.
hypothesis	✅		The ticket includes a proposed direction: 'Include trust message generation capability in test client this cycle to enable manual quality review; delay one of two planned trust messages to manage quality validation workload.' This describes the intended solution approach.
time_budget	✅	Yes	Contains explicit time-budget signal 'This cycle' and clear deliverable 'Test client with trust message generation capability for manual quality review'
test_plan	✅		The ticket explicitly references 'Shan Wu and team' as real users who will manually review trust message quality from 'the test client' before full release. This is a concrete validation plan with named stakeholders and a specific artifact (test client output) to review.
ticket_completeness	✅	Yes	Title has 5 meaningful words ('validate quality of trust messages'). Description has 2+ sentences providing context about the review need and workload management. Deliverable clearly states 'Test client with trust message generation capability for manual quality review' defining what done looks like.

create in project Need to implement open/click tracking functionality for email or messaging system 50% transcript_only

User context	Albert Lie (Forward Labs) and Shan Wu are working on tracking feature; unclear which user segment benefits
Hypothesis	Prototype open/click tracking implementation and validate approach with stakeholders
Deliverable	Research findings, prototype, and plan to share with Shan
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, There, Did, You, Click, Great, Thanks, Research, Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7)
Project	84057572-8079-4dea-8a4e-1962063c4c28
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	While named users are present (Albert Lie, Shan Wu), no specific pain point is articulated. The description mentions 'tracking feature' and 'unclear which user segment benefits' but does not explain what problem these users or segments actually experience that the tracking would solve.
hypothesis	❌		The ticket describes activities (prototype, validate, research) and deliverables but does not include a proposed direction or hypothesis about what the solution should be. It lacks a 'we think X' or 'proposed approach is Y' statement.
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks/cycles), no priority level (P0/P1/P2), and no clear deadline. While there is a deliverable mentioned (research findings, prototype, plan), there is no associated deadline date.
test_plan	❌		The ticket mentions validating with 'stakeholders' (Albert Lie and Shan Wu) but does not specify concrete validation activities with real users, customers, or live data. No specific testing approach, user segment, or data comparison is detailed.
ticket_completeness	✅	Yes	Title has 7 meaningful words exceeding 4-word threshold. Description contains 2 sentences providing context about stakeholders and work status. Deliverable section clearly defines what 'done' looks like: research findings, prototype, and stakeholder plan.

create in project Need a systematic way to capture and prioritize reactive user feedback alongside intentional product features 50% transcript_only

User context	Users providing feedback on features like reach, drag, follow, and import functionality; Hakeem is assigned to work on this
Hypothesis	Distinguishing between intentional product features and reactive user-driven requests will help prioritize work, particularly around email update and import timeliness
Time budget	P0 or P1 priority; some items can be deferred for now
Deliverable	Research plan and prototype for capturing reactive user feedback
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Click, Hakiem Aulia (Linear:1ca29403-c25e-4b6e-b952-47881d3ce0d2, Slack:U06T1PFJHKQ), Reminder, Nothing, There
Project	e0c07324-6699-4cd7-b05d-e0a5465f220f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named user 'Hakeem' is mentioned (a), and specific pain point is identified: difficulty distinguishing between intentional product features and reactive user feedback, which affects prioritization of work around email updates and import timeliness (b).
hypothesis	❌		The ticket describes the problem and desired outcome but does not include a proposed direction, hypothesis, or 'we think the solution is X' statement. It mentions a deliverable (research plan and prototype) but not a hypothesized approach to the solution.
time_budget	✅	Yes	Contains explicit priority signal (P0 or P1) that implies urgency and size, plus clear deliverable (Research plan and prototype for capturing reactive user feedback)
test_plan	✅		The ticket references 'Users providing feedback' and mentions specific features (reach, drag, follow, import functionality) and specific concerns (email update and import timeliness) that imply real user feedback, though it doesn't explicitly name individual users or describe a specific validation approach. The mention of Hakeem being assigned and the focus on 'reactive user-driven requests' suggests real user input, but lacks explicit validation plan details like 'contact X users' or 'test with Y customers.'
ticket_completeness	✅	Yes	Title has 6 meaningful words exceeding the 4-word threshold. Description contains 3 sentences providing context about user feedback, feature prioritization, and current constraints. Deliverable clearly states 'Research plan and prototype for capturing reactive user feedback' which defines what done looks like.

create in project Items that don't require tracking keep reappearing in the system, causing repeated waste of time on dismissing non-actionable items 60% transcript_only

User context	Albert Lie and Shan Wu dealing with AI-generated raw data that creates noise in their workflow
Hypothesis	Implement a persistent dismissal mechanism so that dismissed items don't resurface on refresh/next week
Time budget	next week
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Dismiss, Meaning, You
Project	3c10928b-7e74-4b21-adc5-12deccdcb0c1
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named users identified (Albert Lie and Shan Wu) and specific pain point described (AI-generated raw data creating noise, dismissed items reappearing causing repeated waste of time)
hypothesis	✅		The description includes a proposed solution: 'Implement a persistent dismissal mechanism so that dismissed items don't resurface on refresh/next week' which clearly states what they think the solution should be.
time_budget	✅	Yes	Contains explicit time-budget signal: 'next week'
test_plan	❌		The ticket mentions real users (Albert Lie and Shan Wu) and their workflow problem, but contains no specific validation plan referencing these users or live data. There is no mention of testing with them, checking their sessions, or validating the solution against their actual workflow after implementation.
ticket_completeness	✅	Yes	Title has 15 meaningful words exceeding the 4-word threshold. Description provides 2 sentences of context about the problem and solution. Acceptance criterion is present: 'dismissed items don't resurface on refresh/next week' clearly defines done.

create in project Users cannot easily dismiss items in the problem-digest bot; need a simpler dismissal mechanism 65% transcript_only

User context	Slack users receiving problem-digest bot notifications
Hypothesis	Implement X-emoji reaction dismissal as the primary interaction pattern instead of clicking links
Deliverable	Slack X-emoji dismissal feature implemented in problem-digest bot
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Forward Labs, Click, Slack, Implement Slack
Project	e0c07324-6699-4cd7-b05d-e0a5465f220f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	Identifies a segment ('Slack users receiving problem-digest bot notifications') but lacks a specific named pain point. The description states what needs to be built (X-emoji dismissal) rather than the concrete problem users experience (e.g., 'users spend excessive time navigating dismissal links' or 'current dismissal process is unintuitive').
hypothesis	✅		The description includes a proposed solution: 'Implement X-emoji reaction dismissal as the primary interaction pattern instead of clicking links' - this clearly states the hypothesized direction for solving the problem.
time_budget	❌	Yes	No explicit time-budget signal, priority level, or deadline present. The ticket has a clear deliverable but lacks temporal constraints or urgency indicators needed to assess scope and scheduling.
test_plan	❌		The ticket contains no validation plan that references real users, customers, or live data. It mentions 'Slack users receiving problem-digest bot notifications' as context but provides no specific validation approach such as testing with named users, checking actual Slack usage metrics, or comparing behavior before/after with real data.
ticket_completeness	❌	Yes	Title passes (≥4 meaningful words: 'Users', 'cannot', 'easily', 'dismiss', 'items', 'problem-digest', 'bot', 'simpler', 'dismissal', 'mechanism'). However, description fails: it contains only 1-2 fragmented statements rather than ≥2 sentences of context explaining the problem/background. The description reads more like bullet points than connected sentences. While a deliverable is present, the lack of proper contextual sentences in the description is a failure.

create unclassified Unclear workflow logic for handling feedback in channels when using emoji reactions (e.g., archive, resolve) causing confusion about whether feedback was accepted or rejected 55% transcript_only

User context	Shan Wu - when returning to a channel, unclear what emoji reactions mean or what action was taken on feedback
Hypothesis	Implement a documented logic system where specific emoji reactions (like 'resolve') trigger clear state changes and indicate feedback status
Deliverable	Ticket to define emoji reaction workflow logic and document current flow
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Open, Resolve, Hmm, Current
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named user 'Shan Wu' is identified, and the specific pain point is clearly stated: unclear what emoji reactions mean and what action was taken on feedback, causing confusion about whether feedback was accepted or rejected.
hypothesis	✅		The description includes a proposed direction: 'Implement a documented logic system where specific emoji reactions (like 'resolve') trigger clear state changes and indicate feedback status.' This is a tentative solution statement indicating what should be done to address the problem.
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks/cycles), no priority level (P0/P1/P2), and no deadline mentioned. The deliverable is vague ('Ticket to define...') without a target completion date.
test_plan	❌		The ticket mentions 'Shan Wu' as a real user who experienced the problem, but the validation plan only calls for 'documented logic system' and 'define emoji reaction workflow logic' with no specific plan to validate the solution with Shan Wu, PostHog data, live channels, or any other concrete user/customer validation method.
ticket_completeness	✅	Yes	Title has 16 meaningful words exceeding the 4-word minimum. Description provides 2 sentences of context about the confusion. Deliverable clearly states what 'done' looks like: define emoji reaction workflow logic and document current flow. All three criteria are met.

create in project Users cannot plan for next cycle in the current system, forcing all work into the current cycle and creating planning inefficiency. 75% transcript_only

User context	Shan Wu and team members using Relay/Cycle Planner tool for sprint planning; they need to distinguish between current cycle, next cycle, and roadmap items.
Hypothesis	Rename 'Javis' to 'Cycle Planner' and restore the ability to create and view next-cycle tickets, mirroring the previous Relay functionality.
Deliverable	Rename Javis to Cycle Planner; enable next-cycle ticket creation
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Which, Javis, You, Cyrolight, Then, Relay, Rename Javis, Cycle Planner
Project	e0c07324-6699-4cd7-b05d-e0a5465f220f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Includes named user (Shan Wu and team members) and specific pain point (cannot plan for next cycle, forcing all work into current cycle, creating planning inefficiency)
hypothesis	✅		The ticket includes a proposed direction: 'Rename Javis to Cycle Planner and restore the ability to create and view next-cycle tickets, mirroring the previous Relay functionality.' This is a clear 'we think the solution is X' statement.
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks/cycles), no priority label (P0/P1/P2), and no deadline mentioned. While there is a clear deliverable listed, it lacks any temporal constraint or urgency indicator.
test_plan	✅		Ticket references Shan Wu and team members as real users who need this functionality for sprint planning, indicating validation will occur with actual users of the Relay/Cycle Planner tool.
ticket_completeness	✅	Yes	Title has 13 meaningful words exceeding the ≥4 requirement. Description provides 2+ sentences of context explaining the user need and tool usage. Deliverable section clearly states what 'done' looks like: rename Javis to Cycle Planner and enable next-cycle ticket creation. All three criteria are met.

create in project Naming and UI friction for the cycle planning tool is creating unnecessary cognitive load and extra clicks for frequent operations 55% transcript_only

User context	Internal team (Shan Wu, Albert Lie at Forward Labs) who will use the cycle planning tool repeatedly - potentially hundreds of times over upcoming cycles
Hypothesis	Rename 'Javis' to a shorter name (considering 'Cycle Planner' or 'QR') and streamline the UI to reduce clicks when selecting users and linking projects automatically
Time budget	next cycle or multi-cycle
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Support, Can, Javis, One, Cycle Planner, You, Cycle, Cyreal, Because, Every, Use, Does, Buy
Project	d8c139a7-ab1f-4c87-86a0-ef187085917a
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Both elements present: (a) named users 'Shan Wu, Albert Lie at Forward Labs' and (b) specific pain points 'naming friction creating cognitive load' and 'extra clicks for frequent operations'
hypothesis	✅		The description includes a proposed direction: 'Rename 'Javis' to a shorter name (considering 'Cycle Planner' or 'QR') and streamline the UI to reduce clicks when selecting users and linking projects automatically' - this is a clear 'we think the solution is X' statement.
time_budget	✅	Yes	Ticket explicitly contains time-budget signal 'next cycle or multi-cycle' in the Budget field
test_plan	✅		The ticket references real users (Shan Wu, Albert Lie at Forward Labs) who will use the tool repeatedly and are identified as the validation audience for this change.
ticket_completeness	✅	Yes	Title has 14 meaningful words describing the problem. Description provides 2 sentences of context about the internal team and their usage patterns. Acceptance criteria are present: rename 'Javis' to a shorter name (with options provided) and streamline UI to reduce clicks for user selection and project linking.

create in project UI lacks clarity about recipients, making it unclear who will receive messages or communications 65% transcript_only

User context	End users interacting with the UI; specific user segment not named but implied to be affected by recipient ambiguity
Hypothesis	Getting feature owners to review and address the UI clarity issue
Time budget	Not this cycle
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Not, Nice, Otherwise
Project	84057572-8079-4dea-8a4e-1962063c4c28
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	While a general user segment is implied ('end users'), no named user, customer, or specific segment is explicitly identified. The pain point (recipient ambiguity/UI clarity) is present, but the requirement for BOTH a named entity AND a specific pain point is not fully met.
hypothesis	❌		The ticket describes a problem (UI lacks clarity about recipients) but does not propose a direction, hypothesis, or suggested solution. It lacks a 'we think the solution is X' statement.
time_budget	✅	Yes	Explicit time-budget signal present: 'Not this cycle' clearly indicates this is deprioritized and not scheduled for the current cycle, which is a definitive budget constraint.
test_plan	❌		The ticket contains no validation plan referencing real users, customers, or live data. It mentions 'end users' and 'feature owners' generically but provides no specific names, concrete testing scenarios, or real data comparisons. No actionable validation steps are outlined.
ticket_completeness	❌	Yes	Title passes (5 meaningful words). Description fails: only 2 sentences, neither provides substantive context about the problem. No acceptance criteria, deliverables, or definition of done present.

create in project Unclear process for triaging and prioritizing tickets before check-ins, and ambiguity around what belongs in the backlog versus active work. 55% transcript_only

User context	Project owners (like Luis) need to review and triage grouped tickets to determine what can be worked on versus what should remain in backlog.
Hypothesis	Implement a triage workflow where tickets are grouped by project with clear owners, and establish a clearer distinction between backlog (unconfirmed work) and active problem list (confirmed work to pursue).
Time budget	Not today (deferred decision)
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, You, There, Because, Louise Dungca (Linear:457821c6-bea0-49ae-8bf8-3bc892bf7c12, Slack:U07GYNH7JS2), From
Project	e0c07324-6699-4cd7-b05d-e0a5465f220f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named user 'Luis' (project owner) is identified, and the specific pain point is clearly stated: unclear process for triaging/prioritizing tickets and ambiguity around backlog versus active work categorization.
hypothesis	✅		The ticket includes a proposed direction: 'Implement a triage workflow where tickets are grouped by project with clear owners, and establish a clearer distinction between backlog (unconfirmed work) and active problem list (confirmed work to pursue).' This is a clear statement of the proposed solution.
time_budget	❌	Yes	The ticket explicitly states 'Budget: Not today (deferred decision)' which indicates this is deferred work with no time commitment. No priority level, deadline, or specific time-budget signal (hours/days/weeks) is provided.
test_plan	❌		The ticket describes a process/workflow change with no validation plan. It mentions 'Project owners (like Luis)' but doesn't specify any concrete validation steps like 'Luis will triage X tickets and confirm the workflow works' or 'measure triage time before/after implementation'. Generic process improvements without real user testing or metrics don't meet the criteria.
ticket_completeness	✅	Yes	Title has 12 meaningful words describing the problem. Description has 2+ sentences providing context about project owners needing to review tickets and establishing workflow distinctions. Acceptance criteria are present: implement triage workflow with grouped tickets/clear owners, and establish distinction between backlog and active work.

create in project Unclear definition of when work items are 'finalized' and ready to move from backlog to the product solutions tracking system, causing potential workflow bottlenecks. 55% transcript_only

User context	Albert Lie and Shan Wu (founders at Forward Labs) managing the workflow between backlog and product solutions; future ownership structure may involve other team members making prioritization decisions.
Hypothesis	Define 'finalize' as a binary prioritization decision (work on it or not), tracked in a dashboard bot that monitors items in the Product Solutions column for accountability and progress tracking.
Deliverable	OAuth demo (V0) showing quality message examples in pre-authored demo; decision on whether Luis or another team member should work on V1 with enhanced UX design.
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Turns, There, Because, Etienne Auroux (Linear:e8f6c396-4921-4362-ab74-d6beb0bceada, Slack:U095GPK0YF5), Which, Are, Product Solutions, Anyways, One, Louise Dungca (Linear:457821c6-bea0-49ae-8bf8-3bc892bf7c12, Slack:U07GYNH7JS2), Louise Dungca (Linear:457821c6-bea0-49ae-8bf8-3bc892bf7c12, Slack:U07GYNH7JS2), Louise Dungca (Linear:457821c6-bea0-49ae-8bf8-3bc892bf7c12, Slack:U07GYNH7JS2)
Project	e0c07324-6699-4cd7-b05d-e0a5465f220f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named users present (Albert Lie, Shan Wu, Luis), and specific pain point identified (unclear definition of 'finalized' causing workflow bottlenecks between backlog and product solutions tracking system).
hypothesis	✅		The ticket includes a proposed solution: 'Define 'finalize' as a binary prioritization decision (work on it or not), tracked in a dashboard bot that monitors items in the Product Solutions column for accountability and progress tracking.' This is a clear 'we think the solution is X' statement.
time_budget	❌	Yes	No explicit time-budget (hours/days/weeks), no priority level (P0/P1/P2), and no clear deadline. The deliverable (OAuth demo V0) lacks a target completion date.
test_plan	❌		The ticket mentions Albert Lie and Shan Wu as founders managing the workflow, and references a potential decision about Luis working on V1, but does not include a specific validation plan with real users, customers, or live data. No testing with actual stakeholders, user feedback sessions, or concrete data validation is outlined. The deliverable describes an OAuth demo with 'pre-authored' examples rather than validation against real usage.
ticket_completeness	✅	Yes	Title has 5 meaningful words exceeding the 4-word minimum. Description contains multiple sentences providing context about the workflow issue and team involvement. Acceptance criteria are clearly defined: define 'finalize' as binary decision, implement dashboard bot tracking, and deliver OAuth demo (V0) with decision on V1 ownership.

create in project Unable to demonstrate that the Ghostwriter message quality is better than spam, lacking proof of value to users. 65% transcript_only

User context	Users receiving tracked messages don't see evidence that ghostwritten messages have higher quality than spam, creating uncertainty about the feature's value.
Hypothesis	Work with Albert to create a demonstration or proof point that shows Ghostwriter quality superiority over spam.
Time budget	Next week
Deliverable	Demonstration or proof that Ghostwriter quality is better than spam
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, You, Hakiem Aulia (Linear:1ca29403-c25e-4b6e-b952-47881d3ce0d2, Slack:U06T1PFJHKQ), Because, Well, Then, Cool, Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Ghostwriter, Spain, Nice
Project	42d123ac-e72f-44c1-bece-787c63ff348f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket mentions 'Users receiving tracked messages' as a segment, but lacks a specific named user, customer, or segment identifier (e.g., 'enterprise customers', 'beta testers'). More importantly, while it identifies a pain point about lacking proof of value, it doesn't describe a specific pain point they experience—only that they 'don't see evidence.' The ticket focuses on a product demonstration gap rather than a concrete user problem or pain point they're suffering from.
hypothesis	✅		The ticket includes a proposed direction: 'Work with Albert to create a demonstration or proof point that shows Ghostwriter quality superiority over spam.' This is a clear statement of the intended solution approach.
time_budget	✅	Yes	Contains explicit time-budget signal 'Next week' and clear deliverable 'Demonstration or proof that Ghostwriter quality is better than spam'
test_plan	✅		The ticket explicitly references 'Work with Albert' as a real person to collaborate with on creating the demonstration, which indicates a validation plan involving an actual user/stakeholder rather than generic testing.
ticket_completeness	✅	Yes	Title has 13 meaningful words exceeding 4-word requirement. Description contains 2 sentences providing context about the problem. Deliverable explicitly states 'Demonstration or proof that Ghostwriter quality is better than spam' which clearly defines what done looks like.

create in project Unclear how to track and communicate support relationships between team members on projects 60% transcript_only

User context	Albert Lie and team members (e.g., Hakim) working on projects at Forward Labs need to know who is supporting whom on specific initiatives
Hypothesis	Add a 'supporter' column to the project tracking system, or leverage existing 'leader' and 'team members' fields to explicitly denote support relationships
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Etienne Auroux (Linear:e8f6c396-4921-4362-ab74-d6beb0bceada, Slack:U095GPK0YF5), Hakim, Who, Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU)
Project	e0c07324-6699-4cd7-b05d-e0a5465f220f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named users: Albert Lie and Hakim at Forward Labs (specific team). Pain point: unclear how to track and communicate support relationships between team members on projects.
hypothesis	✅		The description includes a proposed direction: 'Add a 'supporter' column to the project tracking system, or leverage existing 'leader' and 'team members' fields to explicitly denote support relationships' - this is a clear 'we think the solution is X' statement offering potential approaches to the problem.
time_budget	❌	Yes	No explicit time budget, priority level, or deadline mentioned. The ticket describes a feature request but lacks urgency indicators or delivery timeframe.
test_plan	❌		The ticket describes a feature request but contains no validation plan referencing real users, customers, or live data testing. While it mentions Albert Lie and Hakim as context, there is no explicit plan to validate the solution with them (e.g., 'reach out to Albert and Hakim to test the new supporter column'). No mention of PostHog sessions, A/B testing, or any concrete validation steps with real users.
ticket_completeness	✅	Yes	Title has 5 meaningful words describing the problem. Description contains 2 sentences providing context about the need. Acceptance criteria are present: add 'supporter' column or leverage existing fields to denote support relationships.

create in project Need to create and track Linear tickets from Product Solutions 50% transcript_only

User context	Shan Wu and Albert Lie (Forward Labs) need to convert Product Solutions into actionable Linear tickets
Deliverable	Linear tickets created from Product Solutions, verified and shared with Shan
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Linear (Linear:2ccdc7d2-dcee-455d-9252-a8a4ef8a94d6), Product Solutions, Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7)
Project	e0c07324-6699-4cd7-b05d-e0a5465f220f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named users: Shan Wu and Albert Lie (Forward Labs). Pain point: need to convert Product Solutions into actionable Linear tickets (inability to create/track Linear tickets from Product Solutions).
hypothesis	❌		The description states what needs to be done (convert Product Solutions into Linear tickets) but does not include a proposed direction, hypothesis, or suggested solution approach. It describes the task and deliverable without explaining how or why the solution should work in a particular way.
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks/cycles), no priority level (P0-P2), and no deadline date. While there is a clear deliverable (Linear tickets), it lacks temporal constraints needed to assess urgency and scope.
test_plan	✅		The ticket explicitly references 'verified and shared with Shan' as the validation step, naming a real person (Shan Wu) who will verify the deliverable.
ticket_completeness	✅	Yes	Title has 8 meaningful words exceeding the 4-word threshold. Description contains 2 sentences providing context about converting Product Solutions into Linear tickets. Deliverable clearly defines what 'done' looks like: Linear tickets created, verified, and shared with Shan.

create in project Need to select and prioritize which problems to work on and document them with sufficient clarity in Linear 60% transcript_only

User context	Forward Labs team (Albert Lie, Shan, and broader team) needs to evaluate and validate problem statements before proceeding
Hypothesis	Create Linear tickets for identified problems, then review quality and clarity with Shan on Monday, followed by team check-in on Tuesday to finalize priorities
Time budget	Monday PM for clarity review, Tuesday for team check-in
Deliverable	Linear tickets with clear problem statements ready for quality review and team validation
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Forward Labs, Let, Schedule Mon, Linear (Linear:2ccdc7d2-dcee-455d-9252-a8a4ef8a94d6), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Schedule Tue
Project	e0c07324-6699-4cd7-b05d-e0a5465f220f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket names a user/team (Forward Labs team, Albert Lie, Shan) but does not describe a specific pain point they experience. It only describes a process/workflow need (selecting problems, documenting in Linear, review meetings) rather than the actual problem those users face.
hypothesis	❌		The ticket describes tasks and deliverables (create Linear tickets, review quality, team check-in) but does not include any proposed direction, hypothesis, or 'we think the solution is X' statement. It focuses on the process of evaluating and documenting problems rather than proposing how to solve them.
time_budget	✅	Yes	Contains explicit time-budget signals: 'Monday PM' and 'Tuesday' with clear deadlines for review and team check-in. Also specifies deliverable (Linear tickets with clear problem statements) with defined validation checkpoints.
test_plan	❌		The ticket mentions reviewing 'with Shan on Monday' and 'team check-in on Tuesday' but these are internal team reviews of documentation clarity, not validation against real users, customers, or live data. No reference to reaching out to actual users, customers, or testing against real-world data/sessions.
ticket_completeness	✅	Yes	Title has 4 meaningful words ('select and prioritize which problems'). Description contains 2+ sentences of context about team evaluation and validation. Deliverable clearly states 'Linear tickets with clear problem statements ready for quality review and team validation' which defines what done looks like.

create in project Pipeline dependency is blocked on moving a resource to the bulletin board to enable proper linking and execution 50% transcript_only

User context	Albert Lie (Forward Labs) whose pipeline depends on an actual link that requires the resource to be moved to the bulletin board
Hypothesis	Moving the resource to the bulletin board and using copy-paste approach to update the pipeline link
Time budget	Today or Monday morning, with review in the afternoon
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Forward Labs
Project	8c81f339-c24d-4483-bbff-3768e1094b9f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named user 'Albert Lie (Forward Labs)' is identified, and the specific pain point is that their pipeline is blocked because a resource needs to be moved to the bulletin board to enable proper linking and execution.
hypothesis	✅		The description includes a proposed solution: 'Moving the resource to the bulletin board and using copy-paste approach to update the pipeline link' clearly states the intended direction to resolve the blocked dependency.
time_budget	✅	Yes	Clear deadline specified: 'Today or Monday morning, with review in the afternoon' provides explicit time-budget signal indicating urgent same-day or next-morning delivery
test_plan	✅		References Albert Lie (Forward Labs) as a real user whose pipeline will be tested post-ship when the resource is moved to the bulletin board and the link is updated.
ticket_completeness	❌	Yes	Title is adequate with 4+ meaningful words. Description has only 1 sentence of context (the second item is an action, not context). No explicit acceptance criteria, deliverables, or definition of 'done' is provided - only a vague budget/timeline.

create in project Duplicate tracking of team tickets across multiple systems (board/dashboard and Linear) creates redundant work and unclear single source of truth 65% transcript_only

User context	Forward Labs team (Shan Wu and Albert Lie) managing tickets across multiple platforms, experiencing confusion about where to track work
Hypothesis	Consolidate all ticket tracking into Linear as the single source of truth, archive the old board/dashboard, and eliminate manual duplication by translating board items directly to Linear tickets
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Forward Labs, Well, Supporter, Because, Whether, Here, There, Etienne Auroux (Linear:e8f6c396-4921-4362-ab74-d6beb0bceada, Slack:U095GPK0YF5)
Project	e0c07324-6699-4cd7-b05d-e0a5465f220f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named users identified (Shan Wu and Albert Lie) and specific pain point described (confusion about where to track work, redundant manual duplication across multiple platforms)
hypothesis	✅		The description includes a clear proposed direction: 'Consolidate all ticket tracking into Linear as the single source of truth, archive the old board/dashboard, and eliminate manual duplication by translating board items directly to Linear tickets.' This is a specific solution statement.
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks/cycles), priority level (P0/P1/P2), or deadline mentioned. The ticket describes a problem and desired outcome but lacks concrete urgency or scope indicators.
test_plan	❌		The ticket describes the problem and solution but contains no validation plan referencing real users, customers, or live data. There is no mention of testing with Shan Wu, Albert Lie, or anyone else, nor any plan to verify the consolidation works before/after with actual ticket data.
ticket_completeness	✅	Yes	Title has 11 meaningful words exceeding the 4-word minimum. Description provides 2+ sentences of context about the problem (team managing tickets across platforms, confusion about tracking). Acceptance criteria are present: consolidate tracking to Linear, archive old board/dashboard, eliminate manual duplication. All three requirements are met.

create unclassified Lack of a system to track time off and book calls for team members. 50% transcript_only

User context	Internal teams (unnamed) who need to schedule calls and manage time-off tracking.
Hypothesis	Implement a ticketing/tracking system for time-off management to enable better scheduling and planning.
Time budget	Friday night (urgent deadline mentioned for enabling team review and planning)
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Sounds, Because, Forward Labs, But And
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket identifies a segment ('Internal teams') but does not name it specifically, and while it mentions a need (scheduling calls, time-off tracking), it does not describe a specific pain point they experience. The description is generic rather than identifying a concrete problem or consequence they face.
hypothesis	❌		The description states what needs to be done (implement a ticketing/tracking system) but does not include a proposed direction, hypothesis, or explanation of why this solution was chosen. It lacks reasoning like 'we think the solution is X because...' or any tentative hypothesis about the approach.
time_budget	✅	Yes	Contains explicit deadline 'Friday night' marked as urgent, which implies time-budget signal and urgency
test_plan	❌		The ticket contains no validation plan referencing real users, customers, or live data. It mentions 'internal teams (unnamed)' without specific names, no PostHog/analytics checks, no before/after comparisons with real data, and no specific stakeholder testing instructions. Only generic implementation goals are stated.
ticket_completeness	❌	Yes	Missing acceptance criteria or clear definition of 'done'. Title has 4+ meaningful words ✓, description has 2+ sentences of context ✓, but no acceptance criteria, deliverables, or bullets describing completion state ✗

create in project Unable to establish a clear baseline for product engagement metrics (DAU) to measure user activity and guide product roadmap prioritization. 75% transcript_only

User context	Albert Lie and Shan Wu (Forward Labs founders) need to understand how users are actually engaging with their product (Bread CRM) to prioritize improvements.
Hypothesis	Define clear engagement metrics starting with 'weekly active user' and specific feature usage signals (e.g., auto-update, auto-import) rather than relying on ambiguous DAU data; establish baseline first, then drive user calls to validate, then fix identified issues.
Deliverable	Clear definition of weekly active user and engagement tracking metrics for Bread CRM
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Step, Etienne Auroux (Linear:e8f6c396-4921-4362-ab74-d6beb0bceada, Slack:U095GPK0YF5)
Project	b70abc4b-a6c1-4031-8293-eeedeb91629e
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named users: Albert Lie and Shan Wu (Forward Labs founders). Pain point: Unable to establish clear baseline for product engagement metrics (DAU) to measure user activity and guide roadmap prioritization. Both elements are present.
hypothesis	✅		The ticket includes a proposed direction: 'Define clear engagement metrics starting with weekly active user and specific feature usage signals rather than relying on ambiguous DAU data; establish baseline first, then drive user calls to validate, then fix identified issues.' This outlines a hypothesis-driven approach to solving the problem.
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks), no priority level (P0/P1/P2), and no deadline specified. While there is a clear deliverable (engagement metrics definition), the absence of urgency/size indicators means the ticket lacks sufficient scope framing.
test_plan	✅		The ticket explicitly references real users (Albert Lie and Shan Wu, Forward Labs founders) and includes a validation plan to 'drive user calls to validate' identified issues after establishing baseline metrics. This goes beyond generic testing.
ticket_completeness	✅	Yes	Title has 13 meaningful words describing the problem. Description contains 3 sentences with clear context about stakeholders and their needs. Deliverable section explicitly states 'Clear definition of weekly active user and engagement tracking metrics for Bread CRM' which defines what done looks like.

create in project Need to establish a metric threshold for auto-import/auto-update functionality to measure feature adoption or effectiveness. 50% transcript_only

Hypothesis	Set a minimum threshold of more than five auto-imports/auto-updates per week as a success metric; consider tracking both import and update actions since sandbox scanning may trigger status changes.
Time budget	weekly
Deliverable	Metric tracking for auto-import/auto-update counts (possibly named 'AltViews')
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Two, Each
Project	b70abc4b-a6c1-4031-8293-eeedeb91629e
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket describes a metric threshold and tracking requirement but does not identify a named user, customer, or segment experiencing the problem, nor does it articulate a specific pain point they face. It's a feature adoption metric specification without user context.
hypothesis	✅		The description includes a clear proposed direction: 'Set a minimum threshold of more than five auto-imports/auto-updates per week as a success metric' and a hypothesis about what should be tracked ('consider tracking both import and update actions since sandbox scanning may trigger status changes')
time_budget	✅	Yes	Contains explicit time-budget signal: 'weekly' in Budget field, and clear deliverable with success metric threshold (five auto-imports/auto-updates per week)
test_plan	❌		The ticket describes setting up metric tracking and thresholds but contains no validation plan referencing real users, customers, or live data. It mentions tracking 'auto-imports/auto-updates per week' as a success metric but does not specify how this will be validated with actual users or real-world data post-implementation.
ticket_completeness	✅	Yes	Title has 6 meaningful words exceeding the 4-word threshold. Description contains 2 sentences providing context about the metric threshold and tracking considerations. Deliverable clearly defines what 'done' looks like: metric tracking for auto-import/auto-update counts.

create in project Need to establish weekly metrics tracking for campaign performance monitoring 65% transcript_only

User context	Forward Labs team (Albert Lie) needs visibility into auto-import/update and reach metrics (copy+send+Outlook opens)
Hypothesis	Implement automated weekly metrics dashboard tracking both import/update activity and email reach performance
Time budget	weekly cadence
Deliverable	Weekly metrics tracking system for auto-import/update and reach (copy+send+Outlook opens)
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Forward Labs, Implement, Track, Reach, Outlook
Project	b70abc4b-a6c1-4031-8293-eeedeb91629e
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named user/segment: 'Forward Labs team (Albert Lie)'. Specific pain point: lacks visibility into auto-import/update and reach metrics (copy+send+Outlook opens), requiring automated weekly tracking.
hypothesis	✅		The description includes a proposed direction: 'Implement automated weekly metrics dashboard tracking both import/update activity and email reach performance' which describes what should be built to solve the problem.
time_budget	✅	Yes	Contains explicit time-budget signal: 'weekly cadence' indicates recurring work with clear time frequency. Also includes clear deliverable: 'Weekly metrics tracking system' with implicit ongoing deadline structure.
test_plan	✅		Ticket references a real user (Albert Lie from Forward Labs team) and specifies validation through actual metrics they need visibility into (auto-import/update and reach metrics with Outlook opens), indicating real data and user-driven requirements.
ticket_completeness	✅	Yes	Title has 7 meaningful words (✓). Description has 2 sentences providing context about Forward Labs team needs and what to implement (✓). Deliverable clearly states 'Weekly metrics tracking system for auto-import/update and reach' defining what done looks like (✓).

create in project Lack of tracking infrastructure for weekly active user percentage and reach metrics 65% transcript_only

User context	Forward Labs team (Shan Wu and Albert Lie) need to measure user engagement and feature adoption
Hypothesis	Start tracking weekly active user percentage (e.g., % of users with at least minimal usage) and reach metrics (number of copy/send actions) to establish baseline and define goals
Deliverable	Tracking implementation for weekly active user percentage and reach metrics
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Forward Labs, Percentage, Reaching, Let
Project	b70abc4b-a6c1-4031-8293-eeedeb91629e
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named users/team identified: 'Forward Labs team (Shan Wu and Albert Lie)'. Specific pain point identified: 'need to measure user engagement and feature adoption' - they lack tracking infrastructure for weekly active user percentage and reach metrics. Both elements (a) and (b) are present.
hypothesis	❌		The ticket describes what needs to be tracked and measured, but does not include a proposed direction, hypothesis, or suggested solution for how to implement the tracking infrastructure.
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks), no priority level (P0/P1/P2), and no deadline specified. Only a deliverable is mentioned without temporal constraints.
test_plan	❌		The ticket mentions Forward Labs team members (Shan Wu and Albert Lie) who need the metrics, but contains no specific validation plan that references real users, customers, or live data for testing the tracking implementation. It only describes what needs to be tracked, not how it will be validated against actual usage.
ticket_completeness	✅	Yes	Title has 8 meaningful words (≥4). Description has 2 sentences providing context about who needs this and why. Deliverable clause clearly defines what 'done' looks like - tracking implementation for both metrics.

create in project Need to establish tracking and measurement for auto-imported/auto-updated items to understand feature usage and impact 72% transcript_only

User context	Product team (Shan Wu, Albert Lie at Forward Labs) managing metrics around user engagement with auto-import/auto-update functionality
Hypothesis	Track number of auto-imported or auto-updated items as a meaningful metric, ensuring thresholds don't exclude users who are using the feature meaningfully (e.g., 5 uses in a week)
Time budget	Next cycle (immediate action item after metric definition)
Deliverable	Implementation of tracking for auto-imported/auto-updated count metric, assigned to either Etienne or Hakim
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Because, Forward Labs, Let, Who, Etienne Auroux (Linear:e8f6c396-4921-4362-ab74-d6beb0bceada, Slack:U095GPK0YF5), Hakim
Project	b70abc4b-a6c1-4031-8293-eeedeb91629e
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named users/segment: 'Product team (Shan Wu, Albert Lie at Forward Labs)' and 'users who are using the feature meaningfully'. Pain point: Need to establish tracking and measurement to understand feature usage and impact, with concern that thresholds may exclude meaningful users.
hypothesis	❌		The ticket describes what needs to be done (establish tracking and measurement) and mentions a specific threshold example (5 uses in a week), but does not include a clear proposed direction, hypothesis, or solution statement. It lacks a 'we think' or 'we believe' type statement about how to solve the problem or what the underlying cause/solution might be.
time_budget	✅	Yes	Contains explicit time-budget signal 'Next cycle' and clear deliverable 'Implementation of tracking for auto-imported/auto-updated count metric' with assigned owners
test_plan	✅		Ticket references real users (Shan Wu, Albert Lie at Forward Labs) and mentions specific validation approach: tracking meaningful usage thresholds (e.g., 5 uses in a week) to measure actual feature engagement rather than just generic unit tests.
ticket_completeness	✅	Yes	Title has 6 meaningful words ('establish tracking and measurement for auto-imported/auto-updated items'). Description provides 2+ sentences of context explaining the purpose and stakeholders. Deliverable explicitly states 'Implementation of tracking for auto-imported/auto-updated count metric' which defines what done looks like.

create in project Need to establish a baseline measurement for product usefulness by tracking and scanning production more frequently 50% transcript_only

User context	Forward Labs (Albert Lie) and team need to validate how useful their solution is for users
Hypothesis	Implementing more frequent production scanning will help establish a baseline metric for usefulness and improve tracking capabilities
Deliverable	Baseline metric on product usefulness
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Perfect, Forward Labs
Project	42d123ac-e72f-44c1-bece-787c63ff348f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named user/segment: 'Forward Labs (Albert Lie) and team'. Pain point: need to 'validate how useful their solution is for users' and establish baseline metrics, indicating they lack current measurement of product usefulness.
hypothesis	✅		The description includes a proposed direction: 'Implementing more frequent production scanning will help establish a baseline metric for usefulness and improve tracking capabilities.' This is a clear hypothesis about the solution approach.
time_budget	❌	Yes	No explicit time budget (hours/days/weeks/cycles), no priority level (P0-P2), and no deadline specified. The deliverable 'Baseline metric on product usefulness' lacks a target completion date.
test_plan	❌		The ticket mentions 'Forward Labs (Albert Lie)' as a stakeholder but contains no specific validation plan that references real users, customers, or live data for testing. It lacks concrete details like 'reach out to Albert to test', specific metrics to measure, timeline for validation, or how baseline data will be collected and compared. The deliverable is vague ('Baseline metric on product usefulness') without a validation approach.
ticket_completeness	✅	Yes	Title has 6 meaningful words exceeding the 4-word threshold. Description contains 2 sentences providing context about validation and baseline metrics. Deliverable clearly states 'Baseline metric on product usefulness' defining what done looks like.

create in project Track results reporting format was not specified, resulting in unusable daily reports from Serial 75% transcript_only

User context	Shan Wu and the Forward Labs team need to track product metrics (DAU equivalents) but the previous reporting structure didn't provide actionable insights
Hypothesis	Standardize track result format to match DAU reporting structure (Copy Draft, Edit Draft, Open Draft) and use a centralized G-Sheet to track user counts (ESD, U, N)
Time budget	starting next week
Deliverable	Move OAuth dashboard to central sheet and share with Shan
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Now, Forward Labs, Because, Last, Serial, Copy Draft, Edit Draft, Open Draft, Sounds, Sheet, Move, Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7)
Project	42d123ac-e72f-44c1-bece-787c63ff348f
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named users/segment: 'Shan Wu and the Forward Labs team'. Specific pain point: 'track results reporting format was not specified, resulting in unusable daily reports' and 'previous reporting structure didn't provide actionable insights'. Both elements are present.
hypothesis	✅		The ticket includes a proposed direction: 'Standardize track result format to match DAU reporting structure (Copy Draft, Edit Draft, Open Draft) and use a centralized G-Sheet to track user counts.' This is a clear 'we think the solution is X' statement.
time_budget	✅	Yes	Contains explicit time-budget signal 'starting next week' which indicates urgency and approximate scope (1-2 week delivery window). Also has a clear deliverable: 'Move OAuth dashboard to central sheet and share with Shan'.
test_plan	✅		The ticket references real users (Shan Wu and the Forward Labs team) and specifies a concrete validation plan: sharing the centralized G-Sheet with Shan, which implies testing/validation with actual stakeholders who will use the reports.
ticket_completeness	✅	Yes	Title has 7 meaningful words exceeding the 4-word minimum. Description contains 2 sentences providing context about the problem and need. Deliverable 'Move OAuth dashboard to central sheet and share with Shan' clearly defines what done looks like. All three criteria are met.

create in project Unclear whether existing OAuth dashboard is sufficient or if OAuth capabilities need to be centralized across systems 50% transcript_only

User context	Internal team (Hakim has a dashboard); broader platform users who need OAuth onboarding and reach capabilities
Hypothesis	Either the existing Hakim dashboard is adequate, or OAuth functionality should be moved/centralized to a common location to consolidate tooling
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Probably, Forward Labs, Hakim
Project	e89d292d-0ded-4b20-95e0-689014891be6
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	While the ticket names a user (Hakim) and mentions a segment (broader platform users), it does not clearly articulate a specific pain point. The description presents a decision point ('Either X or Y') rather than describing a concrete problem the users experience with OAuth onboarding or reach capabilities.
hypothesis	✅		The description includes a clear hypothesis statement: 'Either the existing Hakim dashboard is adequate, or OAuth functionality should be moved/centralized to a common location to consolidate tooling.' This presents two proposed directions for solving the problem.
time_budget	❌	Yes	No explicit time budget (hours/days/weeks), no priority level (P0-P2), and no clear deadline. The ticket describes a decision point but lacks urgency/size indicators.
test_plan	❌		The ticket describes a decision point about OAuth infrastructure but contains no validation plan. It mentions 'Hakim has a dashboard' and references internal team vs platform users, but provides no concrete plan to validate with actual users, customers, or real data before implementation.
ticket_completeness	❌	Yes	Title has ≥4 meaningful words (pass). Description has ≥2 sentences of context (pass). However, no clear acceptance criteria, deliverables, or definition of 'done' is present—only vague alternatives ('Either...or') without specific outcomes or success metrics (fail).

create in project Need to establish a scalable vocal support system that can transition from manual transcript-based handling to self-managed ticket pipelines as customer base grows. 65% transcript_only

User context	Support team members who currently work off transcripts for a small customer base, but will need to manage their own ticket pipelines when scaling to new customers.
Hypothesis	Create systems/machines to enable support people to own specific areas, self-prioritize, and manage their own ticket pipelines while working from transcripts, preparing for future scale.
Time budget	Future/multi-cycle (mentioned as preparation for when new customers are acquired, not immediate)
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Perfect, Because, Take
Project	d79ab7f6-a066-4064-8a8b-adede7c56fa0
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket identifies a named group (support team members) but lacks a specific pain point. It describes a future scaling need rather than a concrete problem they currently experience. The description is about system capability rather than a named user/segment's actual pain point.
hypothesis	❌		The ticket describes the problem (need for scalable support system) and desired outcome (self-managed ticket pipelines) but does not include a specific proposed direction, hypothesis, or 'we think the solution is X' statement. It lacks a tentative solution or implementation approach.
time_budget	✅	Yes	Contains explicit time-budget signal 'multi-cycle' in Budget field, indicating this is a multi-cycle initiative with future/preparatory nature rather than immediate delivery
test_plan	❌		The ticket describes a future system design but contains no specific validation plan referencing real users, customers, or live data. No mentions of testing with actual support team members, specific customers, or real transcript samples. 'Preparing for future scale' is strategic planning, not concrete validation.
ticket_completeness	❌	Yes	Missing acceptance criteria or clear definition of 'done'. While it has a strong title (≥4 meaningful words) and adequate description (≥2 sentences with context), there are no specific acceptance criteria, deliverables, or bullets defining what successful completion looks like. It describes a need and general approach but lacks concrete success metrics.

create in project Unclear activation target and success metric for user engagement 75% transcript_only

User context	80 users with ~1-2 active users (near 0% activation rate); need to determine what constitutes success
Hypothesis	Use DAU (daily active users) metrics with view count > 1 as the baseline measure of activation, then set a specific percentage target
Time budget	End of April / two weeks
Deliverable	Activation metric definition and target percentage goal
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Two, One, Out, Are, End, Well
Project	546966ce-a9c5-42ac-aa91-974816e14084
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket identifies a segment (80 users) but does not name a specific user, customer, or segment by name (e.g., 'Brian', 'industrial shippers'). It also lacks a specific pain point they experience—instead, it describes a business metric problem (low activation rate) rather than a user-facing pain point or problem the users themselves encounter.
hypothesis	✅		The ticket includes a proposed direction: 'Use DAU (daily active users) metrics with view count > 1 as the baseline measure of activation, then set a specific percentage target goal.' This is a clear 'we think the solution is X' statement about how to measure activation.
time_budget	✅	Yes	Contains explicit time-budget signal ('End of April / two weeks') and clear deliverable (Activation metric definition and target percentage goal) with deadline
test_plan	❌		The ticket defines success metrics (DAU with view count > 1) and sets a timeline, but does not include a concrete validation plan that references real users, customers, or live data. It lacks specific actions like 'monitor these 5 users', 'validate with customer X', or 'check PostHog data post-launch'. The deliverable is definitional rather than validated.
ticket_completeness	✅	Yes	Title has 6 meaningful words exceeding the 4-word threshold. Description contains 2 sentences providing context about the activation problem. Deliverable section clearly defines what 'done' looks like: activation metric definition and target percentage goal.

create in project CRM data is inaccurate and outdated, with trial users marked as active when they are actually inactive, making user engagement metrics unreliable. 65% transcript_only

User context	Albert Lie (Forward Labs) and Shan Wu are analyzing user engagement metrics and need accurate denominator counts for active users (paid and beta users only, excluding stale trial users).
Hypothesis	Count only paid and beta users with more than one engagement event in a given week as the accurate active user base, excluding trial users that are no longer active but not updated in the CRM.
Deliverable	User engagement analysis filtered by paid/beta status and engagement threshold (more than one event in week one).
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, You, Even, Let, Can, Don
Project	b70abc4b-a6c1-4031-8293-eeedeb91629e
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named users (Albert Lie and Shan Wu) identified with specific pain point: CRM data inaccuracy causing unreliable engagement metrics due to stale trial users incorrectly marked as active.
hypothesis	✅		The ticket includes a clear proposed solution: 'Count only paid and beta users with more than one engagement event in a given week as the accurate active user base, excluding trial users that are no longer active but not updated in the CRM.' This is a specific hypothesis about how to fix the inaccurate data.
time_budget	❌	Yes	Ticket lacks explicit time-budget signal (no hours/days/weeks mentioned), priority level (no P0/P1/P2), or deadline. While a deliverable is stated, there is no associated completion date or urgency indicator.
test_plan	✅		The ticket references real users (Albert Lie from Forward Labs and Shan Wu) who will be using the analysis, and specifies they need accurate counts for their engagement metrics work. This constitutes validation with real users, though it could be more explicit about testing procedures.
ticket_completeness	✅	Yes	Title has 15 meaningful words exceeding the 4-word minimum. Description contains 2+ sentences providing context about the problem and stakeholders. Acceptance criteria are clearly defined: count only paid/beta users with 1+ engagement events weekly, exclude inactive trial users, and deliver filtered analysis by status and engagement threshold.

create in project Determining the appropriate aggressiveness level for OAuth enforcement when only 40-50% of existing users are currently using the new product 50% transcript_only

User context	110 total users, 60 currently using old product, 40-50% adoption rate of new product
Hypothesis	There's a tradeoff between aggressive OAuth enforcement (50% adoption, no skip button) versus a more lenient approach (20% adoption, with skip option)
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Forward Labs, Then, Means, You, Huh
Project	e89d292d-0ded-4b20-95e0-689014891be6
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket identifies a user group (110 total users, 60 on old product, 40-50% on new product) but does not name a specific user, customer, or segment. It also lacks a specific pain point—instead it presents a product decision tradeoff about OAuth enforcement strategy rather than describing a pain point that users experience.
hypothesis	✅		The ticket describes a clear tradeoff between two proposed directions: aggressive OAuth enforcement versus a lenient approach with skip option. This presents alternative hypotheses for how to handle the enforcement strategy.
time_budget	❌	Yes	No explicit time budget, priority level, or deadline mentioned. The ticket describes a decision/tradeoff analysis but lacks urgency signals or time constraints.
test_plan	❌		The ticket discusses adoption rates and trade-offs but contains no validation plan referencing real users, customers, or live data testing. It mentions existing numbers (110 users, 60 on old product) but no plan to reach out to specific people, test with real data, or validate the approach with actual users before shipping.
ticket_completeness	❌	Yes	Title fails - only 3 meaningful words ('Determining appropriate aggressiveness'). Description has 2 sentences but lacks clear acceptance criteria, deliverables, or definition of 'done' - it presents a tradeoff without specifying which approach to take or how success will be measured.

create in project Unclear path to grow active users from 110 to 150+ (50% improvement) and ambiguity about which growth strategy (volume vs. engagement vs. results-focused) should drive the approach 65% transcript_only

User context	Forward Labs product team trying to validate a new product idea by increasing user activation and engagement
Hypothesis	Rather than pursuing a realistic but incremental growth path, define what outcome 'matters' first (proving product concept through volume, deep engagement with few users, or measurable results), then align strategy accordingly
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Are, Forward Labs, Let, Because, Then
Project	546966ce-a9c5-42ac-aa91-974816e14084
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket names a user segment ('Forward Labs product team') but lacks a specific pain point. It describes a business goal (growing users from 110 to 150+) and strategic ambiguity, but does not articulate a concrete pain point these users experience.
hypothesis	✅		The ticket includes a clear proposed direction: 'define what outcome matters first (proving product concept through volume, deep engagement with few users, or measurable results), then align strategy accordingly.' This is a hypothesis about the solution approach - that clarifying the desired outcome should precede strategy selection.
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks/cycles), no priority level (P0/P1/P2), and no clear deadline. The ticket contains a growth target (110→150+ users) and strategic questions, but lacks concrete temporal constraints or urgency indicators needed to assess feasibility.
test_plan	❌		The ticket describes a strategic problem about choosing a growth approach but contains no validation plan referencing real users, customers, or live data. It mentions no specific testing with named individuals, data sources, or post-ship metrics to measure against.
ticket_completeness	✅	Yes	Title has 6+ meaningful words describing the growth challenge and strategic ambiguity. Description contains 2+ sentences providing context about user activation validation and the need to define outcomes. The ticket implies acceptance criteria through 'define what outcome matters first' and the three strategic options (volume, engagement, results-focused), which establish what 'done' looks like.

create in project Unclear whether OAuth and product onboarding should be optional or mandatory for new users trying the new product 55% transcript_only

User context	New product users attempting to connect via OAuth and complete onboarding flow; referenced email connect channel shows low adoption
Hypothesis	Making OAuth and onboarding mandatory (rather than optional) will drive better adoption and validate the new product as a key belief/feature
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Can, Hmm, Would, Well, Because, Fathom, Etienne Auroux (Linear:e8f6c396-4921-4362-ab74-d6beb0bceada, Slack:U095GPK0YF5), Then
Project	e89d292d-0ded-4b20-95e0-689014891be6
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket identifies a general user group ('new product users') and a pain point ('low adoption'), but lacks a specific named user, customer, or segment (e.g., a company name, user persona with a name, or defined customer segment) as required by criterion (a).
hypothesis	✅		The description includes a clear hypothesis: 'Making OAuth and onboarding mandatory (rather than optional) will drive better adoption and validate the new product as a key belief/feature' - this is a proposed direction/solution statement.
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks/cycles), no priority level (P0/P1/P2), and no clear deadline mentioned. The ticket describes a problem and proposed solution but lacks concrete urgency indicators or scope signals.
test_plan	❌		The ticket mentions 'low adoption' of the email connect channel and states that making OAuth mandatory 'will drive better adoption,' but provides no concrete validation plan with specific users, customers, or data sources to test this assumption. No mention of reaching out to real users, checking specific metrics post-ship, or comparing outcomes with real data.
ticket_completeness	✅	Yes	Title has 6 meaningful words exceeding the 4-word threshold. Description contains 2 sentences providing context about low adoption and the rationale for making OAuth/onboarding mandatory. The implicit acceptance criterion is clear: OAuth and onboarding should be made mandatory to improve adoption and validate the product as a key feature.

create in project Low adoption of a mandatory onboarding or connection feature with users clicking skip instead of completing it 72% transcript_only

User context	Current user base (approximately 110 people) where many are skipping the onboarding flow; some users face OAuth/admin approval blockers outside their control
Hypothesis	Make the feature mandatory in the onboarding flow and reframe the messaging to improve adoption, targeting 80-90% completion despite blockers
Deliverable	Updated onboarding flow with mandatory requirement and revised framing
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Blake, Then, Aka, Well, Because, Some, There
Project	e89d292d-0ded-4b20-95e0-689014891be6
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket identifies a segment ('current user base of approximately 110 people') but lacks a named user or specific customer segment label. While it mentions a pain point (users skipping onboarding, OAuth/admin approval blockers), it does not clearly articulate the specific pain point these users experience - only that they skip the feature. The description focuses on a solution rather than the user's underlying problem or need.
hypothesis	✅		The description includes a proposed direction: 'Make the feature mandatory in the onboarding flow and reframe the messaging to improve adoption' - this is a clear hypothesis about the solution (mandatory requirement + revised messaging).
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks/cycles), no priority level (P0/P1/P2), and no deadline mentioned. Only a deliverable is stated without temporal constraints.
test_plan	❌		The ticket mentions a current user base of ~110 people and a target of 80-90% completion, but contains no specific validation plan referencing real users by name, real customer segments, or concrete post-ship measurement methods (e.g., 'measure completion rate via analytics for cohort X', 'get feedback from user Y', 'A/B test messaging variants'). It states what should be measured (adoption) but not how or with whom.
ticket_completeness	✅	Yes	Title has 7 meaningful words describing the problem. Description contains 2+ sentences providing context about user base and current behavior. Deliverable clearly states what 'done' looks like: updated onboarding flow with mandatory requirement and revised framing, plus target metric of 80-90% completion.

create in project Migrating 47 out of 93 paying users to a new portal without clear communication due to lack of screen sharing visibility. 50% transcript_only

User context	Shan Wu and Albert Lie (Forward Labs) discussing migration of 47 paying users from existing system to new portal.
Hypothesis	Need to structure and document the migration plan more clearly to enable remote collaboration and shared understanding of which users/columns are being referenced.
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Forward Labs, Sounds, All, Then, Let, Well, Because, You, Sorry
Project	d79ab7f6-a066-4064-8a8b-adede7c56fa0
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	✅	Yes	Named users (Shan Wu and Albert Lie, Forward Labs), named segment (47 paying users), and specific pain point (lack of screen sharing visibility/unclear communication during migration) are all present.
hypothesis	❌		The description identifies the problem (lack of clarity and documentation) and the need (better structure and documentation) but does not include a proposed direction or hypothesis about what the solution should be. It states what needs to be done without suggesting how or what the approach should be.
time_budget	❌	Yes	No explicit time budget (hours/days/weeks), no priority level (P0/P1/P2), and no clear deadline mentioned. The ticket describes a problem and need but lacks concrete urgency signals or size estimates.
test_plan	❌		The ticket mentions migrating 47 paying users but contains no specific validation plan referencing real users, customers, or live data. It discusses the need for better documentation and communication but does not include concrete steps like 'test with [specific user name]', 'verify data in [customer account]', or 'compare migration results on [real dataset]'. Generic mentions of users without a validation strategy do not meet the criteria.
ticket_completeness	✅	Yes	Title has 14 meaningful words exceeding 4-word threshold. Description provides 2+ sentences of context explaining the migration challenge and need for documentation. Implicit acceptance criterion: 'structure and document the migration plan more clearly' defines done state, though could be more explicit with numbered criteria.

create in project Need to develop OAuth implementation strategy for paid users targeting Fathom integration 50% transcript_only

User context	Paid users of Fathom (targeting approximately 47 users, representing ~50% of user base)
Hypothesis	Implement OAuth-force plan to enable paid users on the new platform point
Deliverable	OAuth-force plan document to be shared with Shan
Mentions	Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Fathom, Draft, Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Yep
Project	e8f967c4-caff-4492-b820-d05ddc66beea
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	While a named segment exists ('paid users of Fathom' / '47 users'), there is no specific pain point articulated. The description states what needs to be done (OAuth implementation) but not what problem users are experiencing that necessitates this solution.
hypothesis	✅		The ticket includes a proposed direction: 'Implement OAuth-force plan to enable paid users on the new platform point.' This is a clear statement of the intended solution approach, even though the description is somewhat unclear in its wording.
time_budget	✅	Yes	Contains explicit deliverable ('OAuth-force plan document') with named recipient (Shan), indicating a clear deadline-oriented commitment, though specific time estimate is absent.
test_plan	❌		The ticket mentions delivering a document to be shared with Shan, but contains no specific validation plan involving real users, customers, or live data testing. There is no reference to testing with actual users, checking real sessions, or comparing outputs with real data.
ticket_completeness	❌	Yes	Title passes (6 meaningful words). Description fails - it's only 1-2 fragmented sentences lacking clear context about why OAuth is needed or what problem it solves. While 'Deliverable' is mentioned, it's vague ('OAuth-force plan document') and doesn't constitute a clear acceptance criterion for what 'done' actually means. Missing proper structure and clarity.

create in project Need to migrate all paid users to OAuth authentication while minimizing user friction and handling failed OAuth cases 75% transcript_only

User context	Paid users currently not on OAuth; users may fail OAuth due to missing admin approvals or personal permission denials during the Composio connection step
Hypothesis	Force all paid users to OAuth through a mandatory migration strategy (potentially with advance announcement), while allowing users to skip if they choose not to grant permissions at the Composio step, and proactively handle failed cases through direct outreach (Hakeem and team calling users)
Deliverable	Task/ticket: Force every paid user to OAuth with minimal user friction; strategy document on implementation approach (announcement timing, forced flow design, skip/fallback options)
Mentions	Albert Lie / 이영덕 / 李英德 (Linear:c37e3fa8-41e6-4597-bd12-f289acf92f3d, Slack:U0565NE8KHU), Shan Wu (Linear:052e68d5-f927-4faf-b0ff-c7d12fc1bad8, Slack:U057F3R7YV7), Forward Labs, Hmm, Fix, Hakiem Aulia (Linear:1ca29403-c25e-4b6e-b952-47881d3ce0d2, Slack:U06T1PFJHKQ), Which, Because, You, Number, Connect, Composio
Project	e8f967c4-caff-4492-b820-d05ddc66beea
Fathom	Watch

Rubric scores

Rule	Pass	Req	Note
user_context	❌	Yes	The ticket identifies a segment ('paid users') but lacks a specific named user or customer example. More critically, it describes a technical requirement (OAuth migration) rather than a pain point the users experience. The pain points mentioned (missing admin approvals, permission denials) are obstacles to implementing the solution, not problems users face that motivate the need.
hypothesis	✅		The description includes a clear proposed direction: 'Force all paid users to OAuth through a mandatory migration strategy (potentially with advance announcement), while allowing users to skip if they choose not to grant permissions at the Composio step, and proactively handle failed cases through direct outreach.' This is a concrete hypothesis about the solution approach.
time_budget	❌	Yes	No explicit time-budget signal (hours/days/weeks/cycles), priority level (P0/P1/P2), or deadline mentioned. Deliverables are identified but without temporal constraints.
test_plan	✅		The ticket explicitly references real team members ('Hakeem and team') who will conduct direct outreach and handle failed OAuth cases with actual users. This goes beyond generic testing and involves real user validation through proactive outreach.
ticket_completeness	✅	Yes	Title has 9 meaningful words exceeding the 4-word threshold. Description contains 2+ sentences providing context about the current state and migration strategy. Deliverables are explicitly listed (task/ticket and strategy document), clearly defining what 'done' looks like.

Fathom Intake Preview