Back to Insights

    Who Decided How Your Software Works: You, or Its Defaults?

    Every system ships with answers to questions nobody asked: who sees what, who changes what. Decide them on purpose before the defaults decide for you.

    November 16, 20269 min read
    business systems
    software rollout
    permissions
    operations
    smb operations
    operational friction
    friction found

    Usually the defaults. Not because anyone chose them, but because nobody chose anything else, and software does not wait for a meeting.

    This is the seventh pattern in Friction, Found, our series on the friction we see most often inside growing companies.

    What does it look like when the software decides?

    Picture an owner who rolls out a shared system to the whole team. The goal is simple: everyone works from the same list of accounts, so anyone can pick up a call, a question or an order.

    Out of the box, each user can see only the accounts assigned to them. Nobody picked that. It was the default, and nobody was asked to change it.

    So the shared system arrives, and nothing in it is shared. Someone takes a call about an account they cannot open, so they walk down the hall and ask the person who can. The team rebuilds the old habit inside the new tool, one hallway question at a time.

    The software did exactly what it was set to do. Nobody decided what it should do.

    Why do defaults end up making business decisions?

    Because every system ships with answers to questions the owner has not been asked yet.

    Who can see which records. Who can edit them. Who approves a discount, a refund or a change to an order. What happens to a person's records when they leave. Each one is a setting, and each setting has a default. The vendor picked those defaults for a typical customer, often the most cautious one, and that customer is rarely you.

    None of those are technical questions. They are questions about how the business runs: who owns the customer, who is trusted with what, where a decision stops. When nobody answers them, the defaults answer them quietly, and the team learns to work around the result.

    Why does nobody notice until after the rollout?

    Because the rollout is scoped as setup, not as decisions.

    The implementation plan says import the data, create the users, train the team. It rarely says "decide who sees what." The person doing the setup is not the person who should make that call, so they leave the defaults alone, which is the reasonable thing to do. The owner assumes the setup handled it. Both are right about their own job, and the decision falls in between. We walked through the order that prevents this in how to sequence a system rollout.

    Then the friction shows up in places that do not look like a settings problem: duplicate records because someone could not find the original, approvals waiting on one person, a report that shows each manager a different total.

    What should be decided before anyone opens the settings?

    A short list, written in plain language, before setup starts:

    • Who needs to see what. By role, not by name.
    • Who can change what, and who only needs to look.
    • Which decisions need a second person, and which do not.
    • What happens to a person's records and access when they leave or change roles.

    Each answer is a sentence or two. Together they fit on one page. That page is the process, and the settings are just where it gets recorded.

    Which parts should be settings and which should be structure?

    The same question comes up when a tool is built rather than bought, and it is worth answering on purpose.

    Some things will change: who sees which records, the sources a report pulls from, the wording on a customer email, the categories, the thresholds. Build those as settings the owner can edit. Then a sensible default is a finished state, not a placeholder, and every future change skips the developer.

    Other things should not move without a conversation: how records relate to each other, what counts as a finished job, where the money is recorded. Build those as structure.

    Decide which is which before the build starts. An owner who has to call a developer to change a label will stop asking for changes, and the tool drifts away from how the business runs. An owner who can change the structure from a settings screen will eventually break something nobody can explain.

    What does deciding on purpose look like?

    It looks like an hour, not a project.

    Sit down with the people who will use the system. Walk through the page of decisions. For each one, ask what happens today, what should happen, and who gets to say. Write the answers down. Then open the settings and record them.

    It also makes the next change easy. Once a decision is written down, changing it later is a conversation and a setting, not an investigation into why the system behaves the way it does. We looked at what happens when nobody does this in why nobody uses the software you paid for.

    Where should you start if you see this in your own company?

    Start before the settings. Pick the one system your team complains about most and write down three decisions it is making for you: who can see what, who can change what, and who has to approve what. If you cannot say who made each one, the software did. Decide them on purpose, then set the tool to match. Process first, then the tool.

    If you want help with that, bring it to a Friction Audit. Give us 45 minutes and we will map the decisions your systems are making by default, which ones matter, and which belong in a setting the owner controls. The Leverage Map that comes out of it is yours to keep.

    Curious how we think about operations work?

    Our alignment framework shows where strategy, work, and systems drift apart, and how to close the gap.

    See the framework

    Related Insights

    Yes, There Is an API. Does It Carry the Numbers You Need?

    The software has an API. The numbers you want may not be in it. What to ask before anyone promises an integration, and what an honest scope looks like.

    Why Can't We Use the Feature the Demo Showed?

    The demo showed it working. Your account does not. The three forms the demo gap takes, and the checks to run before you plan anything on a system.