Skip to main content

Economic Insider

Atul Mohan: Credit Where Credit Is Not Due

By: Atul Mohan, PhD

Why the channels that look most efficient in a dashboard may be capturing demand created somewhere else.

Atul Mohan, PhD, is a senior data and AI executive with more than 24 years of experience turning complex analytics into measurable business outcomes. A Princeton-trained data scientist, he has held leadership roles across American Express, Interpublic Group, Omnicom, Teachers Federal Credit Union, and Brainlabs, building and guiding teams at the intersection of data science, marketing analytics, governance, and AI strategy.

It looks like your best-performing channel. It is mostly taking credit for work done somewhere else.

Pull up almost any paid media report, and brand search will be sitting near the top. Low cost per acquisition. High conversion rate. Excellent return on ad spend. Whatever optimization system you point at that report is going to recommend moving money toward it.

Do that, and your business gets worse. Not because the measurement is sloppy, but because the model is structured wrong in a way that no amount of cleaner data will fix.

Start with what a brand search actually is. Somebody types your company name into a search engine. That person has already decided to consider you. Something made that happen. A television flight, a social campaign, a friend’s recommendation, a product experience from two years ago that they are only now acting on.

The brand search click is where that intent surfaces. It is not where the intent was created.

In causal language, brand search sits on the path between your upper funnel activity and the eventual conversion. It is a mediator. And putting a mediator into a model as an independent variable, right alongside the things that cause it, is a specification error with a well-understood consequence. The mediator absorbs the effect of everything upstream.

Your model is not wrong that brand search converts well. It is wrong about what caused the conversion.

What makes this genuinely dangerous, as opposed to merely incorrect, is the way the damage unfolds over time.

Budget shifts toward brand search. Upper funnel spend gets trimmed. And for a while nothing bad appears to happen, because the demand your previous upper funnel work created is still moving through the system. Brand search volume holds steady. Efficiency metrics look better than they have in years. Somebody gets promoted on the strength of it.

Photo Courtesy: Atul Mohan, PhD

Then, with a lag that depends entirely on your category and purchase cycle, the volume of people searching your brand starts to slide. By the time that shows up clearly in the reporting, the spend that would have prevented it was cut three or four quarters ago, and the person who cut it has a different job and a strong story about the efficiency gains they delivered.

I have watched this cycle run more than once. It is remarkably hard to diagnose from inside the company, because every intermediate metric is improving right up until it is not. There is no moment where a dashboard turns red, and someone raises a hand. There is a slow drift, and then a quarter where the acquisition number misses, and then a search for explanations that lands on the market, the category, the macro environment, anything except a budget decision made a year earlier that looked correct at the time.

There are a few ways to handle it, and none of them are free.

The cleanest is experimental. Turn brand search off in a set of matched geographies and watch what happens to total conversions, not to search conversions. The results tend to be uncomfortable for whoever owns the channel, because a meaningful share of that traffic converts anyway through the organic result sitting directly below the ad.

This test costs very little. It takes a few weeks. The fact that so few advertisers run it says more about organizational incentives than about methodology. Nobody wants to run an experiment whose most likely outcome is that a line item they are responsible for turns out to be less valuable than the report says.

In a mix model, you can specify the structure honestly, treating brand search volume as an intermediate outcome driven by your upper funnel spend rather than as another channel competing on the same footing. This is more work, and it requires you to take an explicit position on the causal graph, which some teams find uncomfortable.

That discomfort is appropriate and worth sitting with. You were taking a position already. Leaving brand search in as an independent input is a causal claim. It is just an unexamined one, and unexamined claims have a way of being wrong in whichever direction is most convenient.

The pragmatic middle path, if the full restructure is beyond what your organization will tolerate, is to split brand from non-brand completely, report them separately, and refuse to let allocation decisions treat them as substitutes for one another. It does not solve the attribution question, but it does stop the slow bleed of budget out of demand creation.

What I would push back on hardest is the most common response of all, which is to acknowledge the problem in a footnote and then carry on reporting brand search as a top-performing channel.

Everybody in the room knows the number is not what it appears to be. The number keeps driving decisions anyway. A caveat that does not change anyone’s behavior is decoration, and I would argue it is worse than no caveat at all, because it lets the organization feel sophisticated about a mistake it is still making. It also gives everyone cover. When the acquisition number eventually misses, several people can point to the footnote and say they had flagged it.

There is a version of this problem that shows up in defensive language, and it is worth addressing because it sounds reasonable. The argument goes that you have to bid on your own brand terms, otherwise competitors will, and you will pay more later to recover traffic you used to get free.

Sometimes that is true. In categories with aggressive conquesting, it can be clearly true. But it is an empirical question with a knowable answer, and most organizations treat it as an article of faith rather than testing it. The geographic holdout answers it directly. You will find out whether your organic result holds the traffic, in which categories, and at what competitive intensity. Running the test converts a belief into a number.

There is a broader lesson here that goes past search.

Any channel that sits close to the conversion will look efficient. Retargeting has the same property. So does email to an existing list. So does organic traffic from a comparison site that only exists because somebody built the brand that people are comparing.

Measurement systems reward proximity to the sale. The further upstream a channel sits, the worse it will look in a report and the more likely it is to be cut first when budgets tighten. Which means the structural bias in your measurement runs in the same direction as the structural bias in a difficult quarter, and those two pressures compound.

That is not a measurement problem you can solve with better tracking. It is structural; it will get worse as tracking signal continues to erode, and the only reliable defense is experimentation. Not occasional experimentation when somebody gets curious, but a standing program with a budget line, run on a cadence, with results that feed back into how the models are specified.

The uncomfortable truth is that the channel your dashboard likes most is frequently the one contributing least. Somebody in your organization should be willing to say that out loud in a budget meeting, and be prepared to prove it.

About The Author

Atul Mohan, PhD, is a data and AI executive whose work spans data science, marketing analytics, measurement strategy, and the translation of complex technical systems into business decisions.

Designing for Complexity: How Product Design Shapes Financial Decision-Making

By Shawn Mars

Financial products are often expected to do something deceptively difficult: make highly complex systems easier to use without making them less complete.

In consumer technology, simplicity is frequently treated as an obvious design goal. Fewer steps, fewer choices, cleaner interfaces, and faster interactions are often associated with better experiences. In financial technology, however, simplicity is not always so straightforward.

Financial professionals may need to evaluate large amounts of information, compare multiple scenarios, monitor changing conditions, move through approval processes, and make decisions that carry meaningful consequences. The complexity is not necessarily a flaw in the product. Often, it comes from the work itself.

For product designer Shuchen Wang, whose career has included financial technology work at Goldman Sachs and now continues in financial services at Evercore, this distinction is central to designing professional products.

“Good design in finance is not about removing complexity,” Wang says. “It is about making complexity understandable and navigable.”

That idea challenges a common assumption about product design. The goal is not always to show less. Sometimes the more important task is to help users understand more, faster.

Complexity and Confusion Are Not the Same Thing

A complex system does not have to feel confusing.

This distinction matters in financial technology because many of the problems users encounter cannot simply be reduced to a few buttons or hidden behind a simplified interface. Professionals may genuinely need access to detailed information, multiple states, historical context, or exceptions before they can make a decision.

The designer’s job, then, is not to pretend that complexity does not exist. It is to give that complexity structure.

Information hierarchy, grouping, labeling, progressive disclosure, visual emphasis, and contextual guidance can all determine whether a dense product feels manageable or overwhelming.

“A professional user may need a large amount of information,” Wang says. “The design challenge is helping them understand what matters first, what changed, and what they need to do next.”

This creates an important difference between complexity and confusion.

Complexity may be inherent in the domain. Confusion often comes from the way information is presented.

Good product design instead creates a clear mental model around that complexity.

The user should be able to answer basic questions quickly:

What is happening?

What requires my attention?

What has changed?

What can I do next?

What are the consequences of that action?

When those answers are difficult to find, the problem is not necessarily that the financial system is too complex. It may be that the product has failed to communicate the complexity effectively.

Design Is Also the Design of Attention

Financial professionals rarely suffer from a lack of information.

More often, the challenge is determining which information deserves attention at a particular moment.

A dashboard may contain dozens of metrics. A workflow may include multiple open items. A user may receive updates, alerts, requests, and changes from several directions at once.

In these environments, attention becomes one of the most limited resources.

Product design plays an important role in deciding how that attention is directed.

The size and placement of information, the order in which items appear, the way exceptions are surfaced, the timing of a notification, and the visibility of a change can all influence what a user notices first.

“In information-heavy products, design is partly about helping users allocate attention,” Wang says. “If everything looks equally important, the product is not really helping the user make sense of the information.”

This is why adding more data does not necessarily make a financial product more informative.

A product can technically display everything and still fail to communicate what matters.

The more information a system contains, the more important hierarchy becomes.

Good design creates relationships between pieces of information. It distinguishes routine activity from exceptions, background context from immediate action, and supporting detail from the information that should influence the next decision.

The goal is not simply to reduce cognitive load. It is to help users spend cognitive effort in the right places.

Design Shapes the Environment for Decision-Making

A product designer does not make financial decisions on behalf of the user.

But design inevitably influences how decisions are made.

The order in which information appears can shape what users notice first. A default view can determine which data becomes the starting point for analysis. The visibility of historical context can influence how a current situation is interpreted. The way two options are compared can make similarities or differences easier to recognize.

Even seemingly minor choices such as labels, alerts, and status indicators can affect how confidently a user understands what is happening.

“Design does not make the decision,” Wang says. “But it shapes the environment in which the decision is made.”

This responsibility becomes particularly important in professional software because users are often making decisions under time pressure.

The product has to support fast recognition without encouraging careless action.

This creates a delicate balance.

Designers need to make routine information easy to scan while ensuring that unusual or consequential situations are difficult to overlook. They need to reduce unnecessary effort without hiding information that may change a decision.

In this sense, product design becomes part of the decision infrastructure of the organization.

It determines how information moves from raw data to something a person can understand and act upon.

Why Frictionless Is Not Always Better

Modern digital design often celebrates frictionless experiences.

The logic is easy to understand. If a user can complete an action with fewer steps, less effort, and less waiting, the experience often feels better.

But in financial products, not all friction is bad friction.

Sometimes an extra step exists for a reason.

A confirmation screen may prevent an expensive mistake. A review step may ensure that a user notices an unusual condition. A permission check may protect sensitive information. An approval process may reflect genuine organizational responsibility.

Removing every point of friction can make a product faster while also making it easier to make the wrong decision.

“The goal should not always be to make every action effortless,” Wang says. “Routine actions should be efficient, but consequential actions sometimes need to feel deliberate.”

This leads to a different design principle:

Make the right things easy, and the important things deliberate.

A well-designed professional product should distinguish between unnecessary friction and protective friction.

Unnecessary friction might include repetitive data entry, unclear navigation, redundant steps, or information that users have to search for repeatedly.

Protective friction serves another purpose. It creates a moment to review, confirm, reconsider, or escalate.

The difficulty is knowing the difference.

That requires more than visual design expertise. It requires understanding the underlying work.

Domain Knowledge Becomes Part of Design Expertise

Designing complex financial products requires designers to understand more than interface patterns.

They need to understand why a workflow exists in the first place.

What are users trying to accomplish?

Which decisions carry greater risk?

Who has authority to take a particular action?

Which pieces of information influence that action?

Where do handoffs occur?

What happens when the normal process breaks down?

Without this context, it is easy to optimize the wrong part of a product.

A designer might remove a step that appears redundant without realizing that it serves an important review function. A screen might be simplified in a way that makes it visually cleaner but removes context professionals rely on. A workflow might become faster for one user while creating additional work for another person later in the process.

“The deeper a product sits inside a professional workflow, the harder it becomes to separate design skill from domain understanding,” Wang says.

This does not mean designers need to become bankers, analysts, or financial experts themselves.

It does mean they need enough understanding of the domain to ask the right questions.

For Wang, this has been an important part of working in financial technology.

During her time at Goldman Sachs, she worked on complex, data-heavy financial products designed for professional users. Those environments required more than applying familiar UX patterns. They required understanding how users interpreted information, where complexity came from, and which parts of a workflow could be simplified without removing necessary context.

She now continues her product design career within financial services at Evercore. While the nature of the work evolves across organizations, the broader challenge remains familiar: designing products for people whose work depends on navigating complex information and making informed decisions.

That career path has reinforced her view that good financial product design begins with understanding the work itself.

Designing for Professional Users Requires a Different Mindset

Many widely accepted design principles originated in consumer technology.

Reduce the number of choices.

Minimize clicks.

Keep screens simple.

Remove friction.

Hide advanced functionality until it is needed.

These principles can be useful, but professional products often require a more nuanced interpretation.

A professional user may prefer a dense interface if it allows faster comparison across multiple data points. An additional confirmation step may be appropriate if the action carries meaningful consequences. A workflow may need to expose more states because those states represent real operational differences.

The question should not be whether the product is minimal.

The better question is whether the product helps the user understand and act.

A clean screen that hides important context can be less effective than a dense screen with strong hierarchy.

A shorter workflow can be worse than a slightly longer one if the shorter version removes an important opportunity for review.

And an interface that looks simple can still create significant cognitive effort if users have to remember information that the product could have shown them.

Professional design therefore requires moving beyond simplicity as an aesthetic goal.

The goal is clarity.

The Difference Between Simplicity and Clarity

Simplicity and clarity are often treated as interchangeable concepts, but they are not the same.

Simplicity is about how much is present.

Clarity is about how easily the user can understand what is present.

A financial product can contain a large amount of information and still be clear. It can also contain very little information and remain confusing.

This is one of the reasons Wang believes designers working in complex domains should be careful about simplifying by default.

“Sometimes the best design does not remove information,” she says. “It creates enough structure that users no longer experience that information as overwhelming.”

That structure may come from strong hierarchy, meaningful grouping, contextual explanations, recognizable patterns, or a clear separation between routine information and exceptions.

The designer’s role is to create a path through complexity.

Designing Better Decisions

As financial systems continue to evolve, products will likely contain more data, more functionality, and more interconnected workflows, not less.

That makes the role of product design increasingly significant.

Organizations already have enormous amounts of information. The harder challenge is helping professionals determine what deserves attention, understand what that information means, and act on it appropriately.

In this environment, the value of design extends beyond usability.

It influences how quickly professionals can understand a situation.

It affects whether important changes are noticed.

It determines whether routine work feels manageable.

And it shapes the environment in which decisions are ultimately made.

For Wang, that is what makes designing for financial technology fundamentally different from simply making complex software look simpler.

“Good design in finance is not about hiding complexity,” she says. “It is about giving people a clear way through it.”

The strongest financial products may not be those that remove the most information or reduce every workflow to the fewest possible steps. They may be the ones that understand complexity well enough to organize it around the needs of the people making decisions.

In financial technology, simplicity can be useful.

But clarity is essential.

Learn more about Shuchen Wang’s background and product design work through her professional portfolio. Additional information about her career and experience is available on LinkedIn.