When To Use A Kanban Pipeline View Vs A Relationship-Centric View
A Kanban pipeline board is the right tool for stage-based decisions and the wrong tool for daily relationship work. A relationship-centric view is the right tool for daily triage and the wrong tool for forecast aggregation. The Kanban method itself is borrowed from Toyota’s manufacturing process and described in Anderson and Carmichael’s Kanban: a system designed to make work-in-progress visible, not to surface relationship health. Most consultants use only the first because the second wasn’t a real option until recently.
Have you ever stared at a healthy-looking pipeline and lost a deal you didn’t see coming?
It happens because the Kanban view shows what stage a deal is in, not what’s happening to the relationship behind it. A deal can sit at Stage 4 (Proposal) for two months with steadily declining open rates, two overdue promises, and a champion who quietly changed jobs. The pipeline shows the deal still in Stage 4. Nothing flags. Then the deal dies and the pipeline retroactively shows it moving backward, by which point it’s too late.
If your only view of your active deals is stage-based, you’re missing the variable that actually determines whether they close. Stage tells you where the deal sits in your sales process. Relationship trajectory tells you whether the deal is alive at all. Gartner’s research on B2B buying behaviour consistently shows roughly 80% of the buying journey now happens between stakeholders rather than with the seller, making the relationship layer the dominant signal of whether a deal will land.
Instead of treating “view of pipeline” as a single fixed thing, what if you used different views for different decisions?
Let’s see how.
1. The “Forecast Friday” rule for stage-based work
Some decisions genuinely are stage-based. Weighted forecast aggregation, board reports, identifying which deals have been stuck in one column too long, pipeline coverage analysis - all of these benefit from the Kanban layout where columns equal stages and deals equal cards. The strength of Kanban is that it sums naturally; you can total deal value by column and see the weighted forecast in seconds.
The “Forecast Friday” rule reserves the Kanban view for once-a-week forecast review, monthly board prep, and any moment where you need to communicate pipeline status to someone who also speaks the language of stages. Use it for those, then close it.
The potential is communication efficiency. When your partner, board, or coach asks “how’s the pipeline looking?” the Kanban view answers in 30 seconds. Trying to communicate the same picture through a relationship-centric layout takes 5 minutes and confuses everyone.
Concrete Example: It’s Friday at 4pm. You have a partner check-in at 5pm.
Action Step:
Open Kanban. Sum the column totals. Note any cards that have been in one column for more than 30 days. That’s your forecast. Walk into the meeting. Don’t try to use Kanban for anything else after.
2. The “Daily Triage” rule for relationship work
Most of a consultant’s day is spent on relationship work, not stage-based work. The questions are: who do I need to email today? Which deals are cooling? Which client has gone quiet? Which contacts span multiple deals? Daniel Pink makes the broader point in To Sell Is Human: modern selling is less transaction tracking and more understanding the human dynamics underneath each decision.
The “Daily Triage” rule is to use a relationship-centric view (deals organised around the contacts behind them, with engagement signals surfaced visually) as the first thing you open in the morning. The view should make cooling relationships, multi-deal contacts, and warm-intro paths visible at a glance.
The payoff is catching trouble before the stage moves. A decaying relationship will show declining engagement weeks before the deal backslides on a Kanban.
Concrete Example: You open your Monday morning view and see two contacts whose engagement health has dropped from green to amber over the weekend.
Action Step:
Make the relationship-centric view your default morning view, not the Kanban. The first 60 seconds of your day should answer “what changed in my relationships overnight?” not “where are deals in the pipeline?” The pipeline is always there. The relationships need attention now.
3. The “Decision-First” question to pick a view
The fastest way to know which view to open is to ask what decision you’re about to make, not which view you prefer. Almost every CRM decision falls into one of two categories: stage-based or relationship-based. Picking the right view is a 5-second exercise once you’ve named the decision.
The “Decision-First” question is two prompts: “Am I about to make a stage-based decision (forecast, report, stage triage)?” or “Am I about to make a relationship-based decision (outreach, risk, prep)?” The first opens Kanban. The second opens the relationship-centric view.
The potential is matching the tool to the work. Most consultants default to whichever view they opened last, regardless of what they’re trying to do. That’s how you end up doing daily relationship triage on a Kanban (clumsy and slow) and weekly forecast on a relationship view (confusing and aggregation-resistant).
Concrete Example: You’re about to spend 30 minutes on outbound to your top contacts.
Action Step:
Before opening the CRM, write the decision down. “Daily outbound triage” is relationship-based. Open the relationship-centric view. Don’t be tempted to “just check the pipeline” first. The pipeline is the wrong lens for the decision you’re making.
How Nynch Helps You With This
Most CRMs ship with one view. Nynch ships with both, fully synced, so you can switch between them in one click depending on the decision in front of you.
Pipeline Board view. Classic Kanban with columns for stages. Drag deals between columns. Sum value by column for forecast aggregation. Familiar to anyone migrating from Salesforce, HubSpot, or Pipedrive.
Orbital View. Deals organised around the contacts and relationships behind them. Engagement signals and relationship health rendered visually. Multi-deal stakeholders visible. Decay-based risk surfaces before stage backslides.
Same data, instant switch. Both views show the same live deals. Drag a deal in Pipeline Board and it updates in Orbital View instantly. No syncing, no manual refresh. The view is a lens; the underlying data is unified.
Relationship-health awareness on every card. Even on the Pipeline Board, every deal card shows a relationship-health indicator. The relationship signal is always there, regardless of which view you’re in.
If you’d like to see both views on the same live pipeline so you can decide which one fits how your brain works, book a walkthrough.
Once you’ve picked the right view for the right decision, the next question is what daily and weekly habits actually move pipeline, because the view is only useful when paired with the action.
Read next
- The intent radar — exactly who to call today — read buying signals so your pipeline runs on intent, not guesswork.
- Even If They Are Ghosting You, You Can Still Resurrect the opportunity With This 3-Step Sequence — Don’t accept the ghosting.
- The client command centre — the dashboard consultants actually open every morning to spot risk and expansion early.
Frequently Asked Questions
What is a Kanban pipeline view?
A Kanban pipeline view shows deals as cards organised into vertical columns by sales stage (Discovery, Proposal, Negotiation, Closed). It’s the standard layout used by Salesforce, HubSpot, Pipedrive, and most other CRMs. The strength is that it aggregates naturally for forecast review.
What is a relationship-centric deal view?
A relationship-centric deal view organises deals around the contacts and relationships behind them, with engagement signals and relationship health surfaced visually. The strength is that it makes the relationship trajectory (warming, cooling, decaying) visible at a glance. It is the right view for daily relationship triage.
When should a consultant use a Kanban view vs a relationship view?
Use Kanban for stage-based decisions: weekly forecast, board reports, stuck-deal triage, pipeline coverage analysis. Use relationship-centric for daily decisions: who to reach out to, which deals are at risk because of relationship decay, which contacts span multiple deals, where the warm-intro paths sit.
Why does my pipeline view miss relationship risk?
Because it’s organised by stage, not by relationship trajectory. A deal can sit at Stage 4 with declining open rates, two overdue promises, and a champion who just changed roles. The Kanban view shows a healthy stage. The risk is invisible in that layout. You need a different lens to see it.
Should I switch entirely to a relationship-centric view?
Most consultants end up using both, just at different moments. A relationship-centric view becomes the daily default for triage. The Kanban stays useful for Friday forecasts, monthly reviews, and any reporting where stakeholders also speak the language of stages. The two views complement each other rather than replacing each other.
