Skip to the posts

Writing A 30-part series

Decisions Behind
Businesses

The decisions, trade-offs, and execution problems behind running a business.

Thirty days of observations from inside businesses. On founders, people, customers, AI, and the work that happens between a decision and its outcome.

30 published30 partsBy Yashasvi Shailly

The archive

Start anywhere.

Open a title to read the published text. Each entry includes its original LinkedIn link for images, video, documents and comments. Decision summaries and key pointers are provided separately from the original post text.

01A proposal that went nowhere

Decision discussed

Letting go of founder control

Key pointers

  • Personal-brand dependence
  • Emotional attachment
  • Commitment
  • Delegation

Day 1 of 30: Decisions behind businesses

I was discussing a proposal that went nowhere and got a perspective I had never thought of.

A while ago, I had reached out to an European founder who has built companies on top of their personal distribution.
They have around 200K followers on X alone, and quite a bit across other platforms as well.

The problem they were trying to solve was that their companies were heavily dependent on their personal brand, and they wanted to make these companies standalone.

We discussed everything.
The strategy, the plan, the execution, the budget.
We had even agreed on the pricing.
And when I said, lets get the contract and paperwork done, they stopped replying!
I followed up a couple of times. Still nothing.

I kept wondering what went wrong.
Did I say something wrong?
Did I upset them?
Did I propose something they weren't looking for?
Because we were so far along in the discussion that I couldnt understand what could have gone wrong at that stage.

And I was discussing this with Boardy, and he brought up something I had never considered.
There were two things at play.
One, the paperwork made the commitment real.
Two, the founder was potentially being asked to let go of the very thing that had made their businesses successful.

The companies had been built on the founder's own distribution. Their personal brand was closely tied to the businesses they had built. And suddenly, they were looking at handing over some of that control to someone else.
It is easier to discuss a problem, agree on a strategy, and even have the budget for it.
But actually giving up control of something you have built so dearly and so closely is a completely different thing.

I dont know if this is what actually happened. But the perspective will stay with me.

Usually, when we approach businesses, everything is very practical.
Strategy, operations, budgets, revenue, profits.
We rarely think about the fact that the founder is also human.
A person with emotions, attachments, and a history of everything they have lived through while building that company.

And this conversation is changing how I think about reaching out to founders.
I cannot put myself in their shoes and understand what they are going through. That is very difficult. I haven't lived their experiences.

But the least I can do is consider that the person on the other side of the business discussion is also a human being with emotions.

There is much more to a business decision than just business.

Read Day 1 on LinkedIn # Day 1

Original media, linked context and discussion are available with the post.

029 archetypes of execution stalls

Decision discussed

Diagnosing execution stalls

Key pointers

  • Recurring patterns
  • Nine archetypes
  • Execution bottlenecks

Day 2 of 30: Decisions behind businesses

Across the businesses I’ve worked with, I’ve found recurring patterns in how execution stalls. I’ve grouped them into 9 archetypes.

Different companies, different teams, but some surprisingly familiar situations!

Do any of these archetypes ring a bell?
Perhaps a business you’ve worked with, spoken to or heard about?

Read Day 2 on LinkedIn # Day 2

Original media, linked context and discussion are available with the post.

03Founder conviction and Information Integrity Failure

Decision discussed

Testing founder conviction

Key pointers

  • Information integrity
  • Constructive challenge
  • Psychological safety
  • Bad-news reporting

Day 3 of 30: Decisions behind businesses

In a founder-led company, strong founder conviction is often an advantage.
They've seen the problem up close, made decisions with incomplete information, and built the company from the ground up.

The challenge is making sure the organization has a healthy mechanism for testing those convictions against evidence.

But when that mechanism is weak:
Founder overrides people → People challenge less → Founder receives less contradictory information → Founder becomes more confident in their view → Organization becomes increasingly detached from reality

The founder may not even realize this is happening.
From their perspective, fewer people are disagreeing.
From the organization's perspective, less information is reaching the decision-maker.

That's an Information Integrity Failure.

Common causes:
• Strong founder conviction without sufficient mechanisms for challenge
• Punishment for delivering bad news
• Political incentives
• Weak psychological safety
• Blame-oriented management

Symptoms:
• Employees hide mistakes.
• People don't challenge the CEO.
• Bad news arrives late.
• Meetings contain artificial agreement.
• Leadership is repeatedly surprised.

The goal isn't to prove the founder wrong.
It's to build an organization where the founder can be wrong without people being afraid to tell them.

Read Day 3 on LinkedIn # Day 3

Original media, linked context and discussion are available with the post.

04Sharing context so people can challenge

Decision discussed

Sharing context and inviting challenge

Key pointers

  • Context sharing
  • Safe disagreement
  • Team perspectives
  • Early warnings

Day 4 of 30: Decisions behind businesses

I received pushback on yesterday’s post (below) saying that the real problem is context.
People can’t challenge well when they don’t have the picture the founder has.

It’s a fair point. I think it’s both, and both sit with the founder.

The founder holds the context: the customer call that went sideways, the number that’s slipping. If one person could hold all of it and do all the work, there would be no team.
So getting that context out of the founder’s head is part of the founder’s job. It doesn’t happen by osmosis.

Context makes the disagreement worth having. Safety lets them say so without worrying what it costs them.
No founder has seen every angle. That’s what the team is for. It only works when someone can bring an idea that might fail and not pay for it later.
Context is yours to give. Safety is yours to guarantee.

So, think of the last piece of bad news that reached you. How long had the problem been there before someone told you s

Read Day 4 on LinkedIn # Day 4

Original media, linked context and discussion are available with the post.

05The founder’s bird’s-eye view

Decision discussed

Structuring ownership beyond the founder

Key pointers

  • Founder dependency
  • System ownership
  • Operational leverage
  • Concentrated context

Day 5 of 30: Decisions behind businesses

Even with a Founder's Office and capable operators, founders can struggle to get a true bird's-eye view.

Not saying that the team lacks ability, but because everyone is too close to the day-to-day.

I've been mapping common patterns across early-stage teams, and the same things keep showing up:

- Systems exist, but no one clearly owns them
- Founders stay deep in execution longer than they should
- Operations is treated as support, not as a force multiplier

Nothing here looks like a crisis. That's exactly why it gets missed.

These are silent gaps that don't demand attention and compound anyway.

The Chief of Staff or Founder's Office often steps in help with that missing perspective.
And they do add value.
But they can also introduce a different dynamic:

- High context concentrated in one place
- High impact, but fragile ownership
- A role that exists because something else needs structuring

I'm starting to map these as "reality zones" across founders, operators, and employees.
Ones that decide who grows and who gets stuck.

Read Day 5 on LinkedIn # Day 5

Original media, linked context and discussion are available with the post.

06Leadership creates the conditions for performance

Decision discussed

Creating conditions for performance

Key pointers

  • Role fit
  • Clear expectations
  • Training
  • Coaching
  • Context
  • Authority
  • Incentives
  • Workload
  • Feedback
  • People-system debt

Day 6 of 30: Decisions behind businesses
Unpopular Opinion: Leadership is responsible for creating the conditions under which people can perform.

Before saying, "This employee isn't good enough," leadership should examine:

- Did we hire for the actual role?
- Did the role change?
- Did we explain what good looks like?
- Did we train them?
- Did we give them the necessary context?
- Does their manager coach them?
- Does the role match their capabilities?
- Do they have the authority needed?
- Are incentives pointing in the right direction?
- Have expectations changed without being communicated?
- Are they overloaded?
- Is someone constantly overriding them?
- Are they getting useful feedback?

Only after those questions should you conclude: The person is the problem.

There's also a deeper distinction to be made.

If you repeatedly see: "We hired great people but they don't perform here."
That's a People-System Problem.

If you see: "This person technically owns the outcome, but doesn't have authority or resources."
That's Accountability Failure.

If you see: "Nobody tells this person what good performance actually looks like."
That's People-System Debt.

If you see: "The founder keeps taking their work back because they don't trust them."
That's Founder Dependency.

So the same "employee isn't performing" symptom can have completely different underlying causes.

Read Day 6 on LinkedIn # Day 6

Original media, linked context and discussion are available with the post.

07Why AI pilots stop being used

Decision discussed

Assigning ownership before adopting AI

Key pointers

  • Process ownership
  • Accountability
  • AI adoption
  • Outreach-to-outcome responsibility

Day 7 of 30: Decisions behind businesses

Most UK founders I talk to have already tried AI in their business, and most of them have stopped using it.

Usually it was a tool for outreach or a pilot someone championed in a team meeting.
Three months later, nobody opens it.

The founder's conclusion is usually that AI isn't ready for a business like theirs.
But when you look closer, the problem often isn't AI, the tool was sitting on top of work nobody clearly owned.
Plenty of people had access to it, and no one was answerable for whether it worked.

At a previous setup, we replaced a four-person sales function with operator-led proposals and an AI-led outreach system. In Q1, inbound reached 38% of the previous full year's total. But the bigger difference was having someone own the entire process, from outreach to outcomes.
You cannot automate accountability.

So before you pick the next tool, work out who owns the job you want it to do.

If you're trying to work out where AI is actually worth using in your sales or operations, run it through The One Fix. Link in the first comment.

Read Day 7 on LinkedIn # Day 7

Original media, linked context and discussion are available with the post.

08Accountability without authority

Decision discussed

Delegating authority with accountability

Key pointers

  • Decision rights
  • Pricing authority
  • Scope changes
  • Founder overrides

Day 8 of 30: Decisions behind businesses

It's 9pm and you're rewriting a proposal your sales lead sent over this afternoon.

They're good. You hired them because they're good. But the proposal didn't sound like you, so you fixed it.
You'll probably fix the next one too.

I see this in nearly every founder-led business I work with. The sales lead 'technically' owns revenue, but they can't set a price or agree a scope change without checking with you first. Eventually they stop trying to get it right the first time, because they know it'll come back to them anyway.

That's an Accountability Failure.
Someone owns the outcome without the authority to deliver it.

Hiring a stronger sales lead won't change it. Neither will an AI tool that writes proposals faster, since they'll still be waiting for you at 9pm.

If this sounds like your week, The One Fix will tell you what to change first. Link in the first comment.

Read Day 8 on LinkedIn # Day 8

Original media, linked context and discussion are available with the post.

09AI and campaign sign-off bottlenecks

Decision discussed

Removing campaign approval bottlenecks

Key pointers

  • Founder sign-off
  • Approval delays
  • AI output
  • Decision delegation

Day 9 of 30: Decisions behind businesses

If every campaign still needs your sign-off, putting AI into your marketing team will just add more campaigns onto your desk for approval.

The One Fix tells you which decision has to move before the campaigns do.
Link in the first comment.

Read Day 9 on LinkedIn # Day 9

Original media, linked context and discussion are available with the post.

10Streamlining the customer feedback funnel

Decision discussed

Owning the customer feedback loop

Key pointers

  • Feedback consolidation
  • Owner vacuum
  • Product routing
  • Two-way communication
  • Retention

Day 10 of 30: Decisions behind businesses
I’m “streamlining the funnel” in the picture.

At a previous startup, customer feedback poured in from social media platforms, app reviews, emails and support tickets.
A separate in-app feature sent feedback straight to the CEO’s office by email, bringing in about 20 emails a day.

The neck of the funnel was where it should have reached the product team, and nobody was standing there. No single person owned it, and nothing connected what customers said to what got decided.

In The One Fix terms, this is called an Owner Vacuum.
The work touches every team, so every team assumes another one has it. Customers keep sharing feedback, but nobody owns what happens next.

So I took it on
I built one pipeline that pulled signals from all four channels into one place and routed them back to product.
While working on this, I noticed many users had no email address on file. We could read their feedback, but we couldn’t reply or ask follow-up questions.

So, I pushed for a WhatsApp number and got it set up so the conversation could go both ways, with the idea that it could also help us build a community around the product.

Feedback now had a route into product and retention decisions, with someone responsible for keeping that route working.

Pick one thing your customers tell you every week. Who owns what happens next?
If you can’t name that person, The One Fix will tell you which function to look at first. Link in the first comment.

Read Day 10 on LinkedIn # Day 10

Original media, linked context and discussion are available with the post.

11Founders who schedule interviews on Sundays

Decision discussed

Setting boundaries around weekend work

Key pointers

  • Sunday interviews
  • Founder work habits
  • Work-life boundaries
  • Culture
  • Attrition

Day 11 of 30: Decisions Behind Businesses
This comes from personal experience and observation
Founders who schedule interviews on Sundays.

Yes, you are busy.
Yes, hiring is a big task that often sits with you.
However, this seemingly small thing has deeper roots.

One, it reflects the culture. When the founder treats weekends as work time, weekend work slowly becomes the expectation. HR eventually becomes part of this culture too, either by normalising it or being unable to challenge it.

Second, the founder's work-life balance is off. In fact, it's spilling over into the organisation.
That's natural when you've given the business everything. But people who haven't made that investment shouldn't be held to your pace.
And who can speak up to the founder without fearing for their job?

Early and growth-stage startups often operate this way. Whoever cannot keep up with the all-hustle mode eventually leaves.
But if this continues even after the business has scaled substantially, it can lead to higher attrition, whether employees choose to leave or are eventually asked to.

Attrition starts looking like a people problem when the real cause is organisational.

If you feel your company is heading in this direction, use The One Fix to identify what needs to change first.
Fix the culture before you lose your team, and then your business.

Read Day 11 on LinkedIn # Day 11

Original media, linked context and discussion are available with the post.

12Who owns the pricing decision?

Decision discussed

Naming the pricing decision owner

Key pointers

  • Owner vacuum
  • Approval responsibility
  • Decision ownership
  • Shared documentation

A founder, a Chief of Staff, a Head of Sales and a new hire walk into the same room.
Someone asks, “Who owns the pricing decision?”

The founder says, “I asked the Chief of Staff to handle it.”
The Chief of Staff says, “I was waiting for the founder to approve it.”
The Head of Sales says, “I thought the price in the last updated doc was final”
The new hire asks, “Is there a doc, or do I start one?”

Nobody disagrees on the decision, but no one takes responsibility for making it.
Six weeks later, the decision is still pending, and everyone has been busy with everything else.

The One Fix calls this the Owner Vacuum. It’s one of nine patterns I keep seeing in growing companies, and one of the things the diagnostic is designed to catch.

Put your company through it and tell me whether the diagnosis lands.
Link in the first comment.

This is Day 12 of 30: Decisions Behind Businesses. Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business.

Read Day 12 on LinkedIn # Day 12

Original media, linked context and discussion are available with the post.

13Paying more for an agency doesn’t necessarily buy better thinking

Decision discussed

Outsourcing versus bringing work in-house

Key pointers

  • Agency fit
  • Fees versus value
  • Brief clarity
  • Approval speed
  • Internal capacity
  • Work ownership

Paying more for an agency doesn’t necessarily buy you better thinking.
I learnt this when one agency rejected us for negotiating, and another made us wonder why we’d hired an agency at all.

We were once looking for a social media agency because our existing agency, while doing good work with designs, wasn’t bringing in the engagement we wanted.
We shortlisted a few agencies.

One of them had this very overenthusiastic Gen Z energy. Great pitch and testimonials, but a quote that was double what we were already paying. So obviously, we negotiated.

Getting approval for a slightly higher fee is one thing.
But getting approval for double the amount, especially when there’s no guarantee the work will deliver, is another.

The agency came back, thanked us for negotiating, and rejected us.
Yes, the agency rejected the brand!
They were very clear. Either we work at their quoted price or we don’t work together at all.

We eventually hired another agency at a slightly higher fee than our existing one.
They promised us everything. Strategy, design, execution, content, all of everything you would want.
What followed was 4-5 people from our internal team constantly putting their brains into getting content out of the agency.
They somehow just couldn’t grasp the brief.

It reached a point where you felt like pulling your hair out, sitting down, making the content yourself, and probably getting better engagement.
The final straw was when we were still discussing approval for a time-sensitive post after the moment had passed.

We eventually discontinued the agency and brought the work in-house.
Four people, each already managing their own function, took on the additional responsibility.
I handled the calendar, strategy, coordination and approvals. We divided the execution among ourselves.
It wasn't that we suddenly had more time or resources. We just understood the business, the deadlines and what needed to get done.

I'm not suggesting every company should get rid of its agencies. Plenty of agencies do excellent work, and not every team has the capacity to bring things in-house.
But that experience changed how I think about outsourcing.

It's also something I look at in my consulting work now. Before recommending more people, another agency or a new process, I want to understand why the existing setup isn't working.
Because sometimes the answer isn't to spend more.
It's to change who owns the work.

This is Day 13 of 30: Decisions Behind Businesses. Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business.

Read Day 13 on LinkedIn # Day 13

Original media, linked context and discussion are available with the post.

14Knowing who your customer is doesn’t tell you why they buy

Decision discussed

Segmenting by journeys and motivations

Key pointers

  • Demographics
  • Customer journeys
  • ICP
  • Jobs-to-Be-Done
  • Functional needs
  • Social needs
  • Emotional needs

Knowing who your customer is doesn't necessarily tell you why they buy.

At one of the consumer startups I worked with, we were rethinking how we segmented our customers.
We had been dividing them by demographics, particularly age. But when we examined how people actually interacted with the product, we found considerable overlap.
People across different age groups were following similar journeys, while people within the same age group were using the product differently.

We changed our segmentation approach to account for these customer journeys rather than relying primarily on demographics.
It resulted in better interactions, more clicks, higher engagement, and even a slight improvement in conversions.

But there's another question worth asking.
Even when you know who your customers are and how they use your product, do you know what they're actually trying to accomplish?

This brings me to a framework I find useful: Jobs-to-Be-Done (JTBD).
Popularised by Clayton Christensen and Tony Ulwick, JTBD suggests that customers don't simply buy products. They "hire" them to accomplish something.

And that job can have three dimensions:
Functional: What are they trying to accomplish?
Social: How do they want others to perceive them?
Emotional: How do they want to feel?

Two customers might use the same feature for entirely different reasons.
One wants an answer to make a decision. Another wants reassurance about a decision they've already made.
Same product, similar behaviour, different motivations.

ICP helps you understand who you're selling to. Customer journeys show how they interact with your product. JTBD helps you understand why they're using it in the first place.

If you're a founder, put your business through The One Fix and see what it identifies as the constraints worth addressing first.

This is Day 14 of 30: Decisions Behind Businesses. Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business.

Read Day 14 on LinkedIn # Day 14

Original media, linked context and discussion are available with the post.

15Before replacing someone, establish what is failing

Decision discussed

Diagnosing before replacing an employee

Key pointers

  • Capability
  • Target realism
  • Process quality
  • Input quality
  • Expectations
  • Authority
  • Performance management

One of the easiest decisions to make in business is that someone isn't performing.

The numbers are below target. Deadlines are slipping. Work needs constant corrections.
Replace the person!
Except, what exactly are you replacing them for?

I've worked on rebuilding sales operations, and performance is rarely as straightforward as a dashboard makes it look.
An employee can miss targets because they're not capable of doing the job.
They can also miss targets because the targets are unrealistic, the process is broken, the inputs are poor, or nobody has explained what good performance looks like.

The output can be identical.
The diagnosis isn't.
This distinction matters because businesses often treat performance management as an employee-level decision when the actual problem sits somewhere else.

Consider someone who's accountable for conversion but has no control over lead quality.
Or a manager expected to deliver results while every important decision still needs approval from someone above them.
You can put either person on a performance improvement plan.
But what exactly are you expecting them to improve?

I'm not arguing that every performance problem is a management failure. Sometimes, despite the right conditions, a person simply isn't suited to the role.
That's a legitimate conclusion.
But it should be a conclusion, not the starting assumption.

I've dealt with this while rebuilding sales and operating teams. Sometimes the intervention is performance management. Sometimes it's fixing the process, ownership, or expectations around the person.

The difficult part is knowing which problem you're actually solving.
Before deciding who needs replacing, establish what is actually failing.
Otherwise, you could hire a better person into the exact same problem.

This is Day 15 of 30: Decisions Behind Businesses. Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business.

Read Day 15 on LinkedIn # Day 15

Original media, linked context and discussion are available with the post.

16Some founders won’t acknowledge a problem until it becomes a crisis

Decision discussed

Choosing prospects ready for diagnosis

Key pointers

  • Problem awareness
  • Acceptance
  • Founder blind spots
  • Positioning
  • Prospect qualification
  • Sales effort

Unpopular opinion: Some founders won't acknowledge a problem until it becomes a crisis.

And I learned that trying to convince someone to acknowledge a problem they don't believe exists can be a waste of time, effort, and energy.

When I first started reaching out to founders for The One Fix, my pitch was essentially telling them that there might be something wrong with how their company operates and that they should try it to find out what.

Through those initial conversations, I realised there were two problems with my positioning.
First, I was inadvertently challenging their ego. Nobody particularly likes being told that something might be wrong with the business they've built.
Second, I was expecting them to accept that there was a problem.
And there's a difference between seeing that something is wrong and accepting that something is wrong.

That was my first mistake, and it changed how I positioned The One Fix.

During one of these conversations, a founder told me, "I don't have any blind spots."
And I tried to convince him otherwise.
I explained why founders might miss problems in their own businesses and why an outside perspective could help.

The irony is that I was making the same mistake again, just differently.
I hadn't understood it wasn't productive trying to convince someone who didn't see a problem as a problem.

And in my experience, founders who are absolutely convinced they have no blind spots can be among the hardest to get through to.
Sometimes, the consequences have to become impossible to ignore before the problem is acknowledged.

But that doesn't mean every founder who disagrees with me is in denial. They may genuinely not have the problem I'm trying to solve.
That was the second lesson.
Not everyone who could benefit from your product is someone you should spend time trying to sell it to.
I could keep refining the pitch, explaining the problem, and trying to win the argument.
Or I could spend that time with founders who were already interested in examining what might be holding their businesses back.

And if you're a founder who's certain there are no blind spots in your business, it's worth asking whether that's because you've looked for them or because nobody has challenged you yet.

This is Day 16 of 30: Decisions Behind Businesses. Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business

Read Day 16 on LinkedIn # Day 16

Original media, linked context and discussion are available with the post.

17AI layoffs and the demand loop

Decision discussed

Weighing AI savings against demand

Key pointers

  • Workforce cuts
  • Vendor spending
  • Lost income
  • Reinvestment
  • Purchasing power
  • Demand feedback loop

Canva is restructuring 22% of its workforce.
Microsoft has offered voluntary exits to approximately 60,000 eligible employees.
Google has expanded voluntary buyouts across several countries.
And now Meta is reportedly offering voluntary exits too.

Four companies with different restructuring decisions, all while the technology industry continues investing heavily in AI.
There's a larger economic question behind this that I think deserves more attention.

Why are companies moving towards leaner teams while simultaneously investing heavily in AI?

Tasks that previously required hours of manual execution can now be completed with AI in minutes.
But cost-cutting doesn't begin and end with layoffs.
Businesses are also reconsidering agency contracts, consulting retainers, software subscriptions, outsourcing arrangements and other B2B partnerships.

If something can be done sufficiently well at a lower cost, there's a strong incentive to reconsider what you're paying for it.
For one company, that's a saving. For another, it's lost revenue.
An agency losing clients may reduce hiring. A software company losing subscriptions may cut vendor spending. Those vendors may then reconsider their own expenses.
And employees are part of this equation too.

The people and businesses whose costs companies are trying to eliminate are also customers elsewhere in the economy.

Of course, savings don't disappear. They can be reinvested, passed on through lower prices or used to create new opportunities.
But where those gains go, and how quickly they reach the wider economy, matters.
If enough businesses and individuals lose income faster than they can replace it, spending weakens. Lower demand encourages further cost-cutting.
And the cycle can reinforce itself.

For people waiting for the AI bubble to burst so they can return to working the way they did before, an investment bubble bursting doesn't mean the technology disappears.
Even if AI companies lose valuations or funding, businesses aren't necessarily going to abandon cheaper ways of operating that already work.

Which brings me to the contradiction I am thinking about.
An economy needs more than productive companies. It needs customers who can afford to buy what those companies produce.

I've explored both sides of this argument in a longer piece: Is AI a Bubble? What If It Bursts?

Day 17 of 30: Decisions Behind Businesses
Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business.

Read Day 17 on LinkedIn # Day 17

Original media, linked context and discussion are available with the post.

18Behind the scenes of corporate Diwali gifting

Decision discussed

Giving employees choice in gifts

Key pointers

  • Useful gifts
  • Different life stages
  • Gift cards
  • Leadership buy-in
  • Employee choice

Let me give you a little behind-the-scenes of corporate Diwali gifting.

A few years ago, I was Chief of Staff at a bootstrapped agency, with HR reporting to me.
Diwali was approaching, and we had to decide what to gift the employees.

One unanimous decision across our team was we wanted no candles, company-branded merchandise, chocolate celebration boxes or generic hampers that look impressive but end up sitting in a cupboard.

We wanted to give something people would actually use. Easier said than done!

The problem was that our team included college students doing internships, people early in their careers, and colleagues who were married with school-going children.
Finding one gift that made sense for everyone was difficult.

We considered several options, including cash bonuses, but ruled those out because of added tax implications.
Eventually, we settled on gift cards.

Except the leadership wasn't convinced.
For them, Diwali gifting was about showing appreciation, and a small gift card didn't quite communicate that, even if the amount was decent for a company our size.

I tried explaining it through the three of us: the leadership, HR and me.
We were at different stages of life, with different needs and tastes. Something the leadership would appreciate might mean very little to me. Something HR would love might be something neither of us needed.

If we couldn't agree on what made a good gift among ourselves, why were we trying to decide that for everyone else?
After quite a bit of discussion, the leadership agreed.

We managed to send out the gift cards just before everyone signed off for Diwali.
The team was pleasantly surprised, and people were genuinely thankful to have the choice.
Sometimes, giving people the choice is more useful than choosing for them.

Happy Diwali to all! Hope you got gifts from your company that you can actually use! 😅

Day 18 of 30: Decisions Behind Businesses
Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business.

Read Day 18 on LinkedIn # Day 18

Original media, linked context and discussion are available with the post.

19Must a founder know how to run everything?

Decision discussed

Seeking help as the business grows

Key pointers

  • Founder capability
  • Stage-specific skills
  • Delegation
  • Operational support
  • Responsibility

A founder bluntly told me, "If a founder cannot run their own business, they should shut it down."

I was genuinely surprised.
This came up during my outreach for The One Fix, while speaking to business owners about operational problems and the decisions founders struggle with.

Since when did starting a business mean you must know how to run every part of it, at every stage, without help?

A founder might be excellent at identifying a market opportunity, building a product, or acquiring the first hundred customers.
But the skills required to get a business off the ground aren't necessarily the same ones needed to manage a growing team, build operational processes, handle finances, or scale distribution.
And those requirements change as the business grows.

Someone who could personally manage everything with five employees may struggle to do the same with fifty.
That doesn't automatically make them an incapable founder.
It may mean the business has outgrown the way it was being run.

The responsibility to make sure something gets done doesn't mean you must be the person doing it.
Building a business and knowing how to run it at every stage are two different capabilities.

I didn't argue.

Day 19 of 30: Decisions Behind Businesses
Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business.

Read Day 19 on LinkedIn # Day 19

Original media, linked context and discussion are available with the post.

20A one-person marketing team cannot execute a five-person plan

Decision discussed

Matching marketing plans to capacity

Key pointers

  • Channel prioritisation
  • Time-boxing
  • Content batching
  • Repurposing
  • Automation
  • AI delegation
  • Deliberate exclusions

A one-person marketing team cannot execute a five-person marketing plan.

For over 6 months, I managed Sajhedaar's marketing alongside a day job.
I did this for free (you shouldn't), because I pushed my parents to start the brand.
This was before pre AI era.

So, what did I do as a one-person marketing team?
• Establishing the brand's presence
• Managing the website and social media accounts
• Planning, researching, writing and designing content
• Developing and executing marketing strategies
• Building reviews and referrals
• Tracking website traffic, engagement, resource allocation, leads, conversions and sales

All while figuring out what deserves attention and what isn't working.

Why would a business have just one person handling all of this?
For bootstrapped startups, it's often a financial decision.
Having someone who knows the business, product and audience helps too.

Then comes content creation.
Researching trends, keywords, colour palettes and design directions.
Writing content, finding images, creating graphics and videos, resizing them for different platforms, and sometimes changing the entire narrative to suit the platform.

And how often should you post?
There's no universal answer. It differs by platform, audience and business. You experiment and figure out what works.
I also looked at how other brands approached their content.
What makes their content recognisable, why certain campaigns work, what makes people remember or share them, and which of those ideas can be applied to a completely different business.

How did I manage the workload?
• Planning and time-boxing were essential.
• Developing a marketing strategy that was realistic to execute
• Creating content and social media calendars
• Blocking time to produce content in batches
• Repurposing content across platforms
• Automating repetitive tasks wherever possible
Trello for planning, Canva for design and Zapier for automation helped. Other tools covered research, writing, email and scheduling.

And somewhere between all this, you're also supposed to manage your regular job, sleep, meals, exercise and personal life.

You can have one person handle five functions. That doesn't mean you can expect five-function team-level output from that person.

Today, AI and agents can make a considerable part of this more manageable.
Research, content preparation, reporting and repetitive execution can be delegated to systems.
Of course, someone still needs to set them up, direct them and review their work.
But even with better tools, the marketing plan has to account for the actual capacity available, including which channels and activities the business will deliberately not pursue.

In our case, we eventually couldn't continue with Sajhedaar. I had my own work priorities, and my parents had theirs.

Day 20 of 30: Decisions Behind Businesses
Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business.

Read Day 20 on LinkedIn # Day 20

Original media, linked context and discussion are available with the post.

21When to hire a Chief of Staff: four interview questions

Decision discussed

Hiring a Chief of Staff

Key pointers

  • Difficult relationships
  • Resourcefulness
  • Burnout management
  • Constructive feedback

One important decision in your business is when to hire a Chief of Staff.
Here are four questions I'd recommend asking your candidates.

Having worked as a Chief of Staff three times, I've realised that the title alone doesn't tell you much about how someone will operate.
The role involves working with different kinds of people, navigating limited resources, managing yourself through uncertainty and sometimes handling difficult conversations.

1. Tell me about a specific person you found difficult to work with. What made the relationship difficult, and how did you handle it?
A Chief of Staff works across teams, personalities and working styles.
A strong answer demonstrates self-awareness, an ability to understand different perspectives and how the candidate adapted their approach.
A weak answer places all the responsibility on the other person, without reflecting on their own role in the relationship.

2. Give an example of a time you had to get something done with almost no budget. How did you make it work?
Not every problem comes with the resources to solve it.
A strong response explains how they identified the constraint, found alternatives and delivered an outcome.
A weak response focuses entirely on what they couldn't do because resources weren't available.

3. When you're burnt out or creatively blocked, what do you do?
The role can be demanding and unpredictable. Knowing how someone recognises and manages their own limitations matters too.
A strong answer shows that they recognise when they're approaching their limits, know how to reset and can communicate when priorities need to change.
A weak answer glorifies working through everything without acknowledging the cost or having a way to manage it.

4. How do you usually give feedback when someone you work with is underperforming?
A Chief of Staff may need to influence people without directly managing them.
A strong answer demonstrates the ability to have difficult conversations with specific examples, clarity and respect, rather than making it personal.
A weak answer avoids the conversation, relies on vague criticism or immediately passes the problem to someone else.

None of these questions has one universally correct answer.
But they can help you understand how a candidate thinks, works with people, handles constraints and manages themselves.
And that's worth understanding before you make the hire.

Day 21 of 30: Decisions Behind Businesses
Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business.

Read Day 21 on LinkedIn # Day 21

Original media, linked context and discussion are available with the post.

22Invisible work and capacity

Decision discussed

Accounting for invisible work

Key pointers

  • Follow-ups
  • Cross-team coordination
  • Information gaps
  • Repeated context
  • Emotional labour
  • Context switching

Why does someone who is good at their job still seem to have no capacity left?

Sometimes, it's because a lot of their work never appears in their job description.
• Following up with someone for the third time.
• Getting two teams to agree on something.
• Finding information that should have been shared already.
• Explaining the same context to three different people.
• Making sure something doesn't fall through the cracks.
• Switching between five tasks because everyone needs something urgently.

Businesses are generally quite good at tracking assigned tasks, deadlines, deliverables and outcomes.

But what about the work required to make those things happen?
Who accounts for the time spent coordinating between teams?
Who measures the effort involved in keeping people aligned?
Who notices when one person becomes the unofficial bridge between multiple functions?

This is invisible work: coordination, emotional labour and context switching.
This work is often treated as incidental, even when it's essential to keeping the business running.
And because it isn't formally accounted for, businesses can end up underestimating how much capacity is already being consumed by it.

Maybe the business needs to understand where everyone's time is already going.

Day 22 of 30: Decisions Behind Businesses
Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business.

Read Day 22 on LinkedIn # Day 22

Original media, linked context and discussion are available with the post.

23How managers respond to mistakes

Decision discussed

Responding constructively to mistakes

Key pointers

  • Accountability versus blame
  • Psychological safety
  • Early disclosure
  • Responsibility to fix

How your manager reacts to a mistake determines whether you'll admit the next one

Every organisation talks about accountability.
But accountability and blame are not the same thing.

When people expect to be scolded, embarrassed or held responsible long after a mistake has been fixed, they learn to protect themselves.
They start hiding mistakes, shifting responsibility and waiting until problems become impossible to ignore.

A manager's response sets the precedent.
You can make it safe for someone to admit a mistake without removing their responsibility to fix it.

The goal isn't to build a workplace where nobody makes mistakes. It's to build one where people don't feel the need to hide them.

Day 23 of 30: Decisions Behind Businesses
Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business.

Read Day 23 on LinkedIn # Day 23

Original media, linked context and discussion are available with the post.

24Payment terms belong in expansion strategy

Decision discussed

Choosing markets with cash-flow constraints

Key pointers

  • Payment terms
  • Cash-flow gap
  • Demand predictability
  • Pilot orders
  • Advances
  • Milestone payments

Consider two potential markets.
In one, customers pay in 30 days, but orders are small and unpredictable.
In the other, customers pay in 90 days, but offer larger, recurring contracts.

Your suppliers expect payment in 15 days. You have enough cash to pursue one properly.
Which do you enter first?

The first brings money back sooner. But you may need to keep finding new customers just to maintain sales.
The second offers more predictable demand. But you have to fund delivery long before you collect.
Win several contracts at once, and the opportunity starts asking for more cash than you have.

In a strategy memo I wrote for Bizongo in 2023, I explored six potential industries.
Each had a different reason to be attractive, from growing electronics shipments to specialised packaging requirements in healthcare.

The payment terms above are an illustration, not figures from that memo.
They show a question every expansion proposal needs to answer: how will the business fund the wait?
With suppliers due in 15 days and customers paying in 90, how many orders can you fund through that 75-day gap?
If a recurring customer pays a month late, can you still fulfil their next order?
Do the smaller, faster-paying orders arrive often enough to cover your monthly costs?
And would the larger contracts become viable if customers paid an advance or suppliers gave you 45 days?
The answers could change which market you enter first.

You might pursue the larger contracts, but start with a pilot. Negotiate milestone payments. Accept fewer orders until collections establish a pattern.
Or use the smaller orders to build the cash needed for the longer cycle.
Payment terms belong in the expansion strategy.

Day 24 of 30 : Decisions Behind Businesses
Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business.

Read Day 24 on LinkedIn # Day 24

Original media, linked context and discussion are available with the post.

25A 30-minute meeting with 10 people costs five hours

Decision discussed

Choosing who attends a meeting

Key pointers

  • Decision-makers
  • Contributors
  • Informed stakeholders
  • Person-hours
  • Preparation
  • Context switching

A 30-minute meeting with 10 people costs your business 5 hours.

And that's before accounting for preparation, context switching and follow-ups.

Before scheduling another meeting, ask yourself:
• Who actually needs to make the decision?
• Who needs to contribute?
• Who just needs to be informed?

Deciding who doesn't need to attend is also a business decision.

Day 25 of 30: Decisions Behind Businesses
Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business.

Read Day 25 on LinkedIn # Day 25

Original media, linked context and discussion are available with the post.

26Employee personal brands and company visibility

Decision discussed

Supporting employees' personal brands

Key pointers

  • Individual identity
  • Creative freedom
  • Confidentiality boundaries
  • Company visibility
  • Hiring
  • Inbound leads

Your next lead might come without mentioning your company

Encourage your employees to to talk about themselves.
Their work (not confidential information, obviously), their personalities, what they enjoy, what they don't, how they manage work and family, what they spend their money on, their dreams and aspirations.

And when someone regularly engages with your employee's posts, pictures or videos, there's a good chance they'll eventually get curious about where that person works.
Which company do they work for?
What does the company do?
Why do they seem to enjoy working there?
Some might explore your products or services. Others might consider applying for a job.
This creates instances for marketing, hiring, employer branding and sometimes even sales.

I've seen this work firsthand.
During one of my Chief of Staff stints, the founder was already generating a significant share of inbound leads through his personal brand.
He understood its value.

So he announced a challenge for employees - Post on LinkedIn for 100 consecutive days and win ₹10,000.

I had around 5,000 followers when I accepted it. By the end of the 100 days, I almost doubled my follower count.
I completed the challenge and won the ₹10,000 (Though the money never reached my account, we will talk about keeping your word another day)

What started as a company challenge also helped me build something of my own.
And I strongly believe businesses should encourage employees to build their individual brands rather than expecting them to promote the company directly.

And no, I don't mean turning everyone's LinkedIn banner into a giant advertisement for the company. That isn't cute.

And to employees taking this up: Remember, you're bringing extra visibility to your company, but please don't erase or dilute your personality just to become an unpaid promoter for it.

Founders, give them the freedom to share their experiences, opinions, interests and ambitions. Just establish clear boundaries around confidential information.
They develop an identity beyond their designation.

Your company benefits from the visibility, credibility and relationships they build.
And unlike a campaign that stops when the budget runs out, that presence can continue growing long after the initial effort.

Imagine what that could do for your business over a year.

Day 26 of 30: Decisions Behind Businesses
Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business.

Read Day 26 on LinkedIn # Day 26

Original media, linked context and discussion are available with the post.

27Investing in the perception of progress

Decision discussed

Funding real progress rather than appearances

Key pointers

  • PR spending
  • Budget allocation
  • Leadership priorities
  • Team autonomy
  • Execution

Some startups seem to spend more effort looking successful than becoming successful.

Announce millions in funding. Invest heavily in PR, media coverage and founder interviews.
But when it comes to actually building the business, every rupee needs approval.

There's no focused vision. Every new idea that lands on Instagram Reels feed becomes the next business priority.
Spend aggressively on ads, but acquire barely enough customers to justify the spend.
Set ambitious growth targets, but give teams neither the autonomy to experiment nor the time to see results.
When growth doesn't materialise, blame the employees.
Lay them off, hire new people, and repeat the process.

Funding, talent and effort aren't always the problem.
Sometimes, it's how leadership chooses to use them.

The company keeps investing in the perception of progress while undermining the people responsible for delivering actual progress.

How much of your budget this quarter went into looking successful rather than becoming successful?

Day 27 of 30: Decisions Behind Businesses
Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business.

Read Day 27 on LinkedIn # Day 27

Original media, linked context and discussion are available with the post.

28Avoiding diagnosis does not remove the problem

Decision discussed

Diagnosing problems before they grow

Key pointers

  • Problem avoidance
  • Symptoms versus causes
  • Uncomfortable decisions
  • Founder bottlenecks

During COVID, there was a running joke "If we hadn't gotten tested, we wouldn't have had COVID."

People would get tested out of curiosity, test positive, and suddenly find themselves quarantined.
Had they never taken the test, they joked, it would have remained just another cough and cold.
Of course, not getting tested didn't mean they weren't infected.
But not knowing was certainly more convenient.

I think businesses do something similar.

The founder knows something isn't working.
Revenue is coming in, but profits aren't.
The team is growing, but execution is getting slower.
Everyone is busy, but somehow nothing seems to move.

And yet, diagnosing the problem keeps getting postponed.

Because once you know exactly what's wrong, you have to make a decision about it.
And that decision might be uncomfortable.

It might mean admitting that the strategy isn't working, that an important hire was wrong, or that the founder has become the bottleneck.

So we keep treating the symptoms instead.
Not diagnosing a problem doesn't make it disappear.
It just allows it to become a bigger problem.

Day 28 of 30: Decisions Behind Businesses
Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business.

Read Day 28 on LinkedIn # Day 28

Original media, linked context and discussion are available with the post.

29Why The One Fix chooses one constraint

Decision discussed

Prioritising the first constraint to fix

Key pointers

  • Limited capacity
  • Prioritisation
  • Clear reasoning
  • Product scope

A business can have several things going wrong at once.
Sales are inconsistent.
The team is stretched.
Processes aren’t working.
Cash is tight.

I could build a product that points out all of them.
But one team can only move on so many things at a time. A founder looking at that list would still be left with the same question: What do I fix first?

So I built The One Fix around that question.

It looks for the constraint that needs attention first, explains the reasoning, and suggests what to do next.
That decision also made the product harder to build. A long list gives you room to cover everything.

Choosing one thing means you need to be able to explain why it matters more than the others.

Day 29 of 30: Decisions Behind Businesses
Follow along for more stories about the decisions, trade-offs, and execution problems behind running a business.

Read Day 29 on LinkedIn # Day 29

Original media, linked context and discussion are available with the post.

30Choosing what The One Labs should focus on

Decision discussed

Prioritising The One Labs' next product focus

Key pointers

  • The One Fix
  • The One Job
  • The One Look
  • Shared need to decide what to do next
  • AI as a building tool
  • Product focus
  • Audience input

For 29 days, I’ve written about the decisions that shape businesses.
For the last one, I want to share the thinking behind my own.

The One Fix, The One Job and The One Look solve different problems. B
ut when I look at them together, I see the same starting point: someone is trying to figure out what to do next.

That is what I want The One Labs to build around.

I use AI to build products where it helps.
But the question I keep coming back to is the one the person using it is trying to answer.

I’ve built several ways to help people decide what to do next.
Now I have a decision of my own: which one should The One Labs focus on?

If you were in my place, where would you focus?

Day 30 of 30: Decisions Behind Businesses
That's a wrap!

Keep following me for more stories and insights on business decisions, strategy, operations, and the challenges of building and running businesses.

Read Day 30 on LinkedIn # Day 30

Original media, linked context and discussion are available with the post.

Back to the archive ↑ · More writing