Read the execution pipeline
The execution pipeline lives at https://lengrowth.com/pipeline.
When to use this
Use the pipeline when you need a delivery-focused view. It is more useful than the regular task list if you are trying to answer questions like:
What is ready to start?
What is waiting for my input?
What is already being monitored after delivery?
Which tasks are moving fastest?
Which work came from AI and which came from manual creation?
If the company task list is the board, the pipeline is the delivery lane.
Step-by-step
The pipeline is organized into buckets and stage counts. The top summary can include:
Queued
Active
Waiting
Monitoring
Done
Each card in the pipeline shows a task title and a compact set of labels so you can understand the item without opening the full task detail panel.
The pipeline page also includes a filter toolbar, a visible-count badge, and a "Create task" action.
Make sure the correct company is selected in the header.
Wait for the buckets to load.
Use the filter bar if you want to narrow the view.
If no company is selected, LenGrowth will ask you to choose one first. The pipeline is always company-specific.
The bucket labels are the quickest way to understand the flow.
Queued items are in line to start. They are visible, but they have not moved into active delivery yet.
Active items are being worked on right now. This is where you look for in-progress delivery.
Waiting items are blocked on something. That something might be missing input, a dependency, or a customer reply.
Monitoring items have already been delivered and are being watched for results or follow-up behavior.
Done items are complete. They are useful when you want to review what finished and when it happened.
The page shows counts for each bucket, so you can tell at a glance whether the company has mostly new work, work in motion, or closed work.
The pipeline toolbar gives you the controls you need to isolate one slice of work at a time.
Use the search field to find tasks by title, summary, objective, or channel.
Use the Member filter to focus on one team member.
Use the Stage filter to narrow the pipeline to a specialist request stage.
Use the Status filter to focus on queue, active, done, failed, not priority, or not planned items.
Use the Priority filter to focus on high, medium, or low priority work.
Use the Type filter to focus on one task type.
Use the Source segment to switch between AI and custom work.
Click "Reset filters" when you want the full pipeline back.
The toolbar also shows filter chips for every active filter. Those chips make it easy to remove one constraint without clearing everything.
The Source control has two values:
AI
Custom
Use AI when you want to see work generated or driven by the automated workflow. Use Custom when you want to see work that a person wrote or requested manually.
That split is useful when you are checking whether the pipeline is dominated by generated recommendations or by manually entered work.
The pipeline page includes a "Create task" button.
Click "Create task".
Follow the task creation flow.
Return to the pipeline when the task is saved.
This is the fastest route when you are already thinking in delivery stages and want to add work without leaving the pipeline view.
Pipeline cards are compact, but they still give you several clues about what the work is doing.
Read the card title.
Check the current stage label.
Review any priority or impact badge.
Look for objective and channel labels if they are present.
Read the "Next" line to understand the current next step.
Open the task if you need the full detail panel.
Some cards also show whether the work is connected to a specialist or an AI flow. That helps you tell at a glance whether the task is being handled manually, by a specialist, or by the platform workflow.
When a task changes state, the pipeline updates to match the new stage. You should expect cards to move between buckets as work starts, blocks, resumes, gets monitored, and finishes.
If the pipeline is filtered, only the matching subset appears. That is why a task might seem to "disappear" when it is really still present in the board, just hidden by your current filter settings.
If no cards appear, either the company has not started work yet or your current filters are hiding everything. Clear the filters first. If the board is still empty, go back to the company workspace and run diagnostics again.
Check the company selector and the Source filter. The pipeline is company-specific, and the source filter can hide custom or AI work.
Blocked items usually need input or have an unresolved dependency. Open the task detail panel to see what the current blocker is.
Common problems
Drag horizontally on the pipeline area. On desktop, the board is designed to scroll sideways so you can inspect every bucket.
Related articles