Appearance

Projects

From customer signal to shipped improvement.

Turn questions and observations into work with context. Connect your board, backlog and sprints to tickets and recordings in Meetlead.

Explore the product in a demo tailored to your business.

Meetlead Projects board with demonstration UX tasks, priorities and assigned teammates.
The sprint board shows tasks, work stages and the people responsible.
Capabilities

Bring product work closer to customers.

A useful improvement starts with understanding the problem. With a linked ticket or recording, your team sees both what to do and why it matters now.

The original need

Keep the original problem with the task.

A customer conversation explains why a change matters. Keep the description, priority, owner and ticket link on the task so the team knows where to start.

The type of work
Distinguish tasks, bugs and user stories without maintaining separate lists in other tools.
What done means
Record the expected outcome and how to verify it in the description. Comments preserve decisions.
Issue details with description, assignment and a link to the customer case.
Issue details with description, assignment and a link to the customer case.
Board and ownership

See what is in progress and who owns it.

The board organizes work by status. Adapt columns to your process and filter the view to discuss an owner, issue type, priority or epic.

Your workflow stages
Keep planned, ongoing and completed work clear while defining the statuses you need.
A view for the team meeting
Narrow the board when a decision concerns one area rather than reviewing every issue.
Board with workflow stages, filters and assigned owners.
Board with workflow stages, filters and assigned owners.
Planning the work

Separate incoming ideas from the work you commit to now.

The backlog holds future work. A sprint sets a near-term scope and epics group work around larger goals. Every new idea does not need to become an immediate commitment.

Sprint goal and dates
Name the goal, set dates and choose the scope. Each website runs one active sprint.
Close without losing unfinished work
Move unfinished work to the backlog or another planned sprint.
Active sprint with a goal, dates and progress summary.
Active sprint with a goal, dates and progress summary.
Evidence and links

Show the moment that needs a fix.

A recording helps reproduce the difficulty and links describe how it relates to other work. A task can retain a ticket, recording and blocker or duplicate relationship.

Return to the source
The team opens the linked session instead of inferring every step from a description.
Relationships visible from both sides
Blocks, is blocked by and duplicate links explain why issues should be considered together.
A session recording can provide context for an issue.
A session recording can provide context for an issue.
Review after release

A completed task is the start of reviewing its effect.

After release, return to the original question. Review a goal in Analytics and examine new visits. The next decision rests on behavior, not merely a Done status.

A shared definition of the outcome
Record what should change for users and where you will check it.
Connected tools with distinct roles
Projects organizes delivery. Analytics, recordings and conversations help assess the change.
Explore Analytics
An Analytics funnel helps review the goal after work is completed.
An Analytics funnel helps review the goal after work is completed.

For your team

See how the product fits everyday work.

A fix reported by a customer

Link a bug to its ticket and recording. A developer can inspect what happened while support follows the work status.

A small team’s sprint

Select priority work from the backlog and give the sprint a goal. The board shows progress and unfinished work is organized when the sprint ends.

A UX review informed by conversations

Group similar difficulties in an epic, describe hypotheses and assign tasks. After shipping, review a relevant goal in Analytics.

Projects

Capabilities

A board that makes work visible

Organise tasks, bugs and stories by status. Set a priority and assignee so every next step has an owner.

A backlog and a sprint rhythm

Collect ideas in the backlog, plan sprints and select work for the active sprint. Epics connect tasks around a larger goal.

Context at the source

Link tasks to tickets, recordings and other tasks. Mark dependencies, blockers and duplicates without leaving the issue behind.

Decisions you can return to

Comments and change history retain team decisions. See who changed a status, priority or the scope of a task.

A view that answers your question

Filter work by assignee, type, priority or epic. Move from the whole board to the scope you need to discuss with the team.

A workflow that fits your team

Configure statuses and board columns. Keep planned, ongoing and completed work clear while adding the stages your team needs.

How it works

Close the customer feedback loop.

  1. Capture the signal

    A customer asks how to download a PDF. The conversation and recording help describe the real obstacle.

  2. Give the improvement direction

    Create a task, link its context and set a priority. Plan it in the backlog or a sprint.

  3. Move the work through the board

    Assign an owner, update status as work progresses and record decisions in comments. Links show whether another issue blocks completion.

  4. Check the result

    Ship the change and monitor the relevant goal in Analytics. Use the evidence to choose your next step.

Availability

Projects is an installable App with access determined by your plan or workspace permissions. Each site has one project and can run one active sprint.

See pricing
FAQ

Good to know

Which kinds of work can I track?

Tasks, bugs and stories. Each has a status, priority, assignee and history, and can belong to an epic and a sprint.

Can I link a session recording to a task?

Yes. Tasks can link to tickets, recordings and other tasks, keeping the original problem alongside the work.

Can one website have multiple projects?

The current model is one project per site. Its backlog, epics and sprints organise multiple initiatives within the same product.

Can I work without sprints?

Yes. The backlog holds planned work, organized by status, priority and owner. Start a sprint when you want a shared scope and goal for a period.

What happens to unfinished sprint work?

When completing a sprint, move unfinished issues to the backlog or a planned sprint. Each website can have one active sprint at a time.

How do I distinguish a blocker from a duplicate?

Issue links distinguish blocks, is blocked by, related and duplicate relationships. They appear on both issues so the context remains clear from either card.

Keep the next good improvement in sight.

Tell us about your team. We will show you the product and help you choose capabilities for the way you work.

Explore the product in a demo tailored to your business.