Yoganath V

An empty screen signals no value, no direction and no reason to stay, making a blank dashboard a decision moment rather than a placeholder.

• The same logic applies to any first screen: when the value is not obvious in seconds, users do not click, scroll or stay.
• The rule: the first screen must answer what the user should do and why now.

A demo runs smoothly until a CEO opens the product for the first time, finds no data, history or activity, and asks what he is supposed to do.

• Nobody answers.
• In a SaaS onboarding audit described in the same post, a dashboard showed “No data available” with no guidance or action, and users left within seconds.
• The redesign added a plain statement explaining the space, a suggested next action and a visual cue showing what success looks like.
• The post reports that activation improved and drop-offs fell.

Read original · Original 2

In their account, more visibility creates confusion and slows decisions; the usual problem is premature complexity, not missing features. They describe progressive disclosure as decision architecture, not a UI trick: map what the user must decide now, what can wait and what should never be shown, then reveal complexity only when intent appears.

In a SaaS onboarding audit, 12 fields appeared upfront, along with advanced settings and several early choices.

• Users hesitated, skipped and abandoned.
• Showing only three critical inputs first, hiding advanced options until users signaled intent and revealing complexity later reportedly raised completion and cut support tickets.

Read original

A redesign can look clean and still change nothing if the work is confined to one role.

• They name five roles that drive impact: researcher, strategist, simplifier, systems thinker and communicator.
• Teams that measure output rather than outcomes, the post argues, underuse design.
• Design connects directly to product strategy, revenue goals and business intelligence.

In a product review, engineering blamed unclear specs, product blamed slow design, and design said it had delivered everything.

• Yoganath V argues that all three were right—and that was the problem.
• A SaaS platform redesign produced clean UI, consistent components and faster flows, yet adoption did not improve and support tickets stayed high.
• The post attributes this to the designer wearing only one hat.

Read original

The filter has three questions: Is the input tied to user behaviour?

• Does it align with product strategy?
• Which business intelligence metric will it affect?
• They call input that fails these tests noise and warn that it compounds faster at design-system scale.

In a B2B SaaS onboarding project, several stakeholders gave input, design incorporated it all, the flow became “complete” and conversion dropped. A design review can follow the same pattern: product pushes back, stakeholders add “just one more thing,” the designer becomes defensive, and the meeting closes with “let's iterate” without anything improving.

Read original

Users who do not engage are called distracted or impatient; the deeper reading is that they saw no immediate value.

• Designers who underperform are called failing; the deeper reading is that their role was defined too narrowly.
• The posts shift the explanation from user behaviour or individual weakness to decision clarity and role structure.
• One tension remains: designers are urged to expand their remit into strategy and communication, while stakeholder input should be filtered hard.
• That asks designers to be both more involved and more selective.

A review shows no clicks, no scroll and 70% drop-off in 15 seconds, leading the team to conclude that users are not engaging.

• The post reframes the issue as unclear next steps, no reason to expect value ahead and weak trust.
• Its rule: the first screen must answer “what should I do, and why now?”

Read original · Original 2 · Original 3 · Original 4

Start here because it is the most concrete of the posts: it names a specific screen, a specific failure, and a three-step repair a reader can apply the same week.

A product demo goes well: smooth flows, fast-loading data, clean design.

• Then the CEO opens the product for the first time, sees no data, history or activity, and asks what to do.
• Yoganath V argues that empty states aren’t edge cases; for most users, they’re the first experience.
• The example is a SaaS onboarding audit in which a dashboard showed "No data available" with no guidance or action, and users left within seconds.
• The redesign added three things: a clear explanation of the space, a suggested next action, and a visual cue of what success looks like.
• The post reports improved activation and fewer drop-offs.

For brands planning a campaign

Best for campaigns aimed at improving onboarding conversion: a workshop or advisory session on empty-state design can give the client a tangible artifact quickly, and the three-part fix can go straight into a design review. For brands selling onboarding or analytics tools, the post makes a ready-made case for treating the first signed-in screen as a conversion surface.

Start here if the reader wants a testable change — fewer fields, later complexity — rather than a general plea for simplicity.

The post opens with a team proud to show every feature and option, and leadership pleased with the completeness, while users drop off in 30 seconds.

• Yoganath V argues the opposite of the common intuition: more visibility means more confusion and slower decisions, not more control.
• The example is a SaaS onboarding audit with 12 fields upfront, advanced settings visible and multiple early choices; users hesitated, skipped and abandoned the flow.
• The fix was progressive disclosure: show only three critical inputs first, hide advanced options until users signal intent, and reveal complexity only when needed.
• The post reports a jump in completion rate and fewer support tickets.

For brands planning a campaign

The closest fit for an onboarding-conversion brief: the change is form-level and needs no new features. For a talk or audit on progressive disclosure, the "every extra option is a hidden tax" framing can win over stakeholders who resist cutting fields.

Read it after the onboarding pieces if the reader wants the organisational argument sitting behind them.

In a tense product review, engineering blamed unclear specs, product blamed slow design, and design said it had delivered everything.

• All three were right, Yoganath V says—and that was the problem.
• The post contrasts the surface view that UX designers make screens and flows with the deeper claim that they orchestrate decisions across the business.
• A SaaS platform redesign delivered clean UI, consistent components and faster flows, yet adoption didn’t improve and support tickets stayed high.
• Yoganath V names five roles that drive impact—researcher, strategist, simplifier, systems thinker and communicator—and tailors the message to founders, product and design leaders, and rising designers.

For brands planning a campaign

Better suited to a leadership or team-structure conversation than a tactical fix; it supports framing a design engagement around decision-making rather than screen production. If a client asks why a completed redesign didn’t move metrics, the post offers a diagnosis.

Start here for a small framework plus the failure story that shows why the filter exists.

A design review goes wrong in a familiar way: design presents a solution, product pushes back, stakeholders add "just one more thing," the designer gets defensive, the meeting ends with "let's iterate," and nothing improves.

• Yoganath V argues that unstructured feedback kills clarity while mature feedback sharpens decisions.
• The example is a B2B SaaS onboarding project where inputs from several stakeholders were all incorporated, the flow became "complete," and conversion dropped.
• The proposed filter has three questions: is the feedback tied to user behaviour, does it align with product strategy, and which business intelligence metric will it affect.
• If it fails those, Yoganath V calls it noise.

For brands planning a campaign

Relevant when an engagement includes a design review or multi-stakeholder workshop: the three-question filter is portable and takes minutes to apply. It also shows why onboarding changes can fail when teams collect feedback without a rule for deciding what to act on.

Start here if the reader wants the diagnostic reading that sits underneath the onboarding posts.

A review finds no clicks, no scroll and 70% drop-off within 15 seconds, and the team concludes users aren’t engaging.

• Yoganath V reads it differently: users leave because they don’t see immediate value, not because they’re distracted or impatient.
• In a SaaS dashboard audit, users landed on a feature-rich homepage with multiple calls to action and dense information, then froze.
• The post links each behaviour to a cause—no click to an unclear next step, no scroll to no expectation of value ahead, no stay to broken trust—and offers one rule: the first screen must answer "what should I do, and why now?"

For brands planning a campaign

Good supporting evidence for a first-screen or landing-page audit within a broader onboarding brief. The click/scroll/stay framing can also structure a measurement review with a client who tracks only drop-off.

The fix added a clear message explaining what the space was, a suggested next action, and a visual cue for success. They argue that empty states are not edge cases but the first experience for many users, and that poor first-run guidance is a business leak affecting activation and drop-off.

Before-and-after product or onboarding audit; empty-state redesign built around message, action, and success cue.

Ask for the figures, client name, and date behind the reported activation improvement and reduced drop-offs.

For brands planning a campaign

Directly relevant to a B2B SaaS onboarding conversion brief. A talk or advisory session could focus on empty-state strategy, first-run guidance, and activation metrics.

Examples: Source 1

Users hesitated, skipped fields, and abandoned.

• The redesign showed only three critical inputs first, hid advanced options behind user intent, and revealed complexity only when needed.
• They frame progressive disclosure as decision architecture, not a UI trick, and argue that every extra option slows decisions and lowers conversion.

Decision mapping: identify what the user must decide now, what can wait, and what should not be shown.

Ask for the product name, completion and support-ticket figures, and dates behind the reported improvements.

For brands planning a campaign

Useful for a workshop or talk on simplifying onboarding flows, sequencing decisions, and reducing cognitive load in B2B SaaS.

Examples: Source 1

The team read this as users not engaging; they reframe it as users not seeing immediate value.

• The post breaks the behavior into no click because of unclear next steps, no scroll because of no curiosity, and no stay because of weak trust.
• Their proposed rule is that the first screen must answer “What should I do, and why now?”

Behavioral read of drop-off metrics; first-screen audit focused on clarity, curiosity, and trust.

Ask for the source and context behind the 70% figure.

For brands planning a campaign

Relevant to above-the-fold messaging, onboarding entry points, and activation campaigns for SaaS products.

Examples: Source 1

They argue that feedback is not the problem; unstructured feedback is.

• The proposed filter asks whether feedback is tied to user behavior, aligns with product strategy, and names the business intelligence metric it will affect.
• If it fails those tests, it is noise.

Three-question feedback filter anchored in behavior, strategy, and measurement.

Ask for the B2B SaaS onboarding project's name and the measured conversion change.

For brands planning a campaign

Suited to a product and design leadership workshop on review culture, decision hygiene, and avoiding feedback-driven dilution.

Examples: Source 1

The post argues that the surface belief—that UX designers create screens and flows—misses the deeper reality: designers orchestrate decisions across the business.

• It lists five roles that drive impact: researcher, strategist, simplifier, systems thinker, and communicator.
• A SaaS platform redesign delivered clean UI, consistent components, and faster flows, yet adoption did not improve and support tickets stayed high because the designer wore only one hat.

Role taxonomy and outcome-oriented design framing; connects design to product strategy, revenue goals, and business intelligence.

Ask for the platform name and its adoption or support metrics.

For brands planning a campaign

Useful for an advisory or leadership talk on defining design roles, measuring outcomes rather than output, and moving design from execution to decision influence.

Examples: Source 1

They write text-only LinkedIn essays that teach through specific product moments and translate UX choices into business outcomes such as conversion, retention, and support load.

Narrative audit, framework, and audience-specific implications.

The posts show a written LinkedIn format. If video, newsletters, live talks, or long-form articles matter to the brief, ask for samples in those formats.

For brands planning a campaign

A brand can expect structured, example-led explanations that translate design decisions into business metrics, making this a good fit for workshops, talks, or advisory work.

Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5

Read alongside Yoganath V for two working designers' views on where the profession is heading.

Best's posts are tooling and career-market critiques: Figma's release pace, credit limits on AI prototyping, semantic tokens lost on import, and the AI-native alternatives gaining ground. Yoganath V works one level down in the product, on decision architecture, first-run guidance and the business metrics those changes move, and names no tools.

Read original · Original 2

The subject matter overlaps most directly with Yoganath V's posts on understanding the right problem before designing.

Chattopadhyay writes from early-career project experience, a master's programme, stakeholder websites and one art e-commerce case study, describing how they drafted a framed problem in Claude and then rebuilt it from original research. Yoganath V writes frameworks for founders and design leaders, generalising from unnamed product audits into roles, filters and rules rather than telling a single project's story.

Read original · Original 2

Both treat demand and activation as accumulated trust rather than channel activity. Useful for the go-to-market side of the argument they make from the product side.

Kader's material is marketing and sales strategy: the demand generation mistakes behind rising acquisition costs and falling qualified meetings, delivered through video episodes and a downloadable strategy guide. Kader does not cover product or interface decisions, and the format is spoken and promotional rather than a written essay.

Read original · Original 2

The two posts stay on that ground: one argues that Figma's slow innovation pace, prompt caps, and token handling are costing teams time and money, and names a dozen AI-native alternatives; the other maps five design roles onto what AI does to them, moving product designers toward full-stack work, researchers toward research automation, and visual designers toward brand strategy.

• If the team's real leak is that the design tooling cannot keep pace or that the roles they have hired cannot produce the first-run experience, this is the closer starting point.
• For a talk or short advisory engagement to lift onboarding conversion, frame the work as tool and skills planning rather than screen design.

Nothing in the two posts covers activation, empty states, or form design, so the onboarding-conversion question goes unanswered.

• Yoganath V offers a decision rule for a first screen and a test for each form field; Richard Best offers market and career analysis, which is harder to turn into a week of work with an onboarding team.
• The buyer trades a narrow, testable scope for a broad industry argument and should expect the engagement to end in a tooling or hiring recommendation rather than rewritten screens.

Examples: Source 1 · Source 2

The two posts are aimed there: one lists eight demand-generation mistakes — chasing volume over fit, messaging that sounds like everyone else, campaigns with no market focus, optimizing for clicks instead of conviction — and the other explains why the old go-to-market playbook stopped working and what the market changed underneath. If qualified meetings are falling while cost per acquisition climbs, and the signup funnel is starved before it starts, this is the closer starting point for the same decision about where to spend on lifting conversion.

The in-product side of onboarding is absent.

• There is no equivalent of the empty-state rewrite or of sorting each form field into now, later, or never, so the engagement has to be reframed as go-to-market strategy rather than activation design.
• The team may still need someone to do the screens afterwards.
• The commercial shape also differs: TK Kader publishes programs and a downloadable strategy guide, so a defined purchase route exists; ask Yoganath V to scope the engagement in conversation.
• Buying is easier, but the subject moves away from the stated onboarding-conversion need.

Examples: Source 1 · Source 2

The two posts are a graduation notice describing strengths in user research and prototyping, and a piece of project work on framing a problem: rebuilding a problem statement from early research, turning it into a How Might We that holds both user and stakeholder needs, and deliberately not taking the first AI-generated suggestion.

• That is directly useful on a small, defined project where the first-run experience is being designed around an assumption nobody has tested.
• It keeps the same decision about a short engagement aimed at onboarding conversion while shifting its first step to framing and research.

The documented body of work is two posts and one e-commerce case study, so there is far less to judge than with the other alternatives.

• No SaaS onboarding, activation metric, or field-sequence material appears.
• A team that already knows its problem and needs a first-run screen rewritten or a signup form cut will get less from this than from Yoganath V.
• No commercial format is published; ask what the engagement would deliver and how it would be scoped.
• Review the work against the specific problem-framing output, not a conversion figure.

Examples: Source 1 · Source 2