How a Company Should Work: Departments, Budgets, People & Shared Responsibility

Start with the work the customer needs to receive.

An organizational chart can be perfectly tidy while a customer waits three days for an answer. Every box has a title. Every title reports somewhere. The missing information is who can decide what happens next. I would rather begin with that question than spend the first meeting moving rectangles around a screen.

A company needs people to understand the work, the authority behind it and how their contribution connects to someone else’s. Departments help concentrate expertise and develop consistent practices. They also create boundaries, which become expensive when an ordinary customer request has to negotiate them without a guide.

My starting point is a plain objective agreed with the decision makers. What must this business reliably deliver? To whom? At what quality, pace and economics? Then I want to see the path from the first customer promise through delivery, payment, support and renewal. That path reveals where departments need to cooperate and where responsibility has disappeared.

This is my perspective on organizational design, informed by work across strategy, marketing, ERP, Salesforce, AI, data and project leadership. It is a way to reason through the business. The structures and budgets below are hypothetical examples, not universal benchmarks or representations of a client’s finances.

The companion CEO leadership essay addresses the executive making company-wide choices. Here, I am interested in the organization those choices create: the jobs, handoffs, decision rights, development opportunities and resources people live with afterward.

Give each function enough depth to do its job.

Finance needs to tell the business more than what happened last month. The accounting function records and reconciles. Financial planning examines what may happen next. Treasury or the designated cash owner watches liquidity. In a small company these tasks may sit with a few people, but the differences still matter when growth consumes cash faster than the income statement suggests.

Sales and Marketing need shared definitions around suitable customers, accepted opportunities, claims and handoff. Marketing can generate interest in an offer the delivery team cannot support. Sales can close terms that make an apparently attractive customer unprofitable. Operations should participate before a promise becomes a contract, particularly when the work is customized.

Product and engineering should understand the customer problem and the business case, while retaining the ability to challenge a requested solution. Technology and data teams need process owners who can explain what information means. A Salesforce field, an ERP record and a dashboard label can all describe “customer” differently. Somebody must resolve the business definition before the integration faithfully reproduces the disagreement.

Support and customer success are valuable sources of operating evidence. Give them a route to influence product priorities and service design. If the same avoidable question arrives hundreds of times, the company may need a clearer explanation, a product change or a corrected sales promise. Asking the support team to answer faster addresses only one part of the cost.

My CMO, CTO and MarTech architecture essays examine those leadership responsibilities individually. Organizational design connects them to an operating result.

Overlap should produce cooperation and a clear final decision.

Some overlap is necessary. A pricing change can involve Finance, Sales, Marketing, Product and Operations. Trying to eliminate every shared interest would remove useful judgment. The practical question is who makes the decision, who contributes, who executes it and what requires escalation.

A responsibility map can help when it describes actual work. RACI separates the people responsible for doing the work, the accountable owner, those consulted and those informed. It is useful only if the names correspond to authority and availability. Giving a person accountability without budget, access or decision rights is mostly a way of arranging future frustration.

For a hypothetical enterprise proposal, the account executive might coordinate the opportunity, the delivery leader approve feasibility, Finance approve exceptions within a policy and counsel review the agreement. An authorized executive resolves a material exception outside those limits. The customer should not have to discover that arrangement by receiving four incompatible answers.

Write a short decision record for consequential choices. Identify the question, owner, input needed, deadline, result and conditions that would prompt reconsideration. The value lies in preserving reasoning. A team can change course more intelligently when it knows which assumption changed.

Boundaries should also protect focus. Being collaborative does not mean any executive can assign work directly to anyone in the company without discussing priorities. A helpful request still consumes capacity. Route it through the people responsible for deciding what the team should do next.

A career should have more than one direction.

People develop unevenly and often discover an aptitude after joining a company. A support specialist may be excellent at product research. An analyst may become a strong operations leader. A gifted technical contributor may want greater scope without managing a department. The company benefits when those possibilities have a legitimate path.

Lateral movement should be an organized opportunity, not an informal favor. Publish internal openings, explain the relevant skills and give employees a way to explore them. A trial assignment or a defined rotation can reveal whether the work fits. Agree on supervision, duration and the effect on the person’s existing responsibilities.

Managers need an incentive to develop people who may eventually move. If losing a capable employee permanently damages the manager’s staffing plan, talent hoarding becomes understandable even when it hurts the company. Budget for succession and backfill, and recognize managers who help people grow into useful roles elsewhere.

Cross-training also improves resilience. A second person should know how to perform critical tasks, locate the documentation and recognize when specialist help is required. That is different from assuming everyone can perform every job after a short introduction. Some work requires substantial training, authorization or professional qualifications.

Use fair, job-related evaluation and appropriate HR review. The aim is to make opportunity visible and development realistic. An internal candidate deserves more than being told to do two jobs for six months while leadership considers whether the promotion has a budget.

My budget starts with commitments and capabilities.

I would not begin a company budget by assigning fashionable percentages to department names. I would start with the revenue assumptions, delivery requirements, current commitments, cash position and capabilities the strategy needs. Then I would ask what can be supported under a base case and what changes if the forecast is wrong.

Build payroll where the people work, including employer costs and benefits where applicable. Count agency fees, software, facilities and shared services consistently. If a central IT budget covers a platform, do not count the same subscription again in every department’s total. An allocation can explain usage without creating another expense.

The financial model needs separate views of earnings, cash and the balance sheet. The SEC’s introductory guide to financial statements explains those distinctions. An income statement describes performance over a period; available cash also depends on collection timing, investment, financing and other changes.

In my opinion, a sensible budget visibly funds delivery quality, essential controls, maintenance and development of people as well as growth. It should show which spending maintains existing operations and which spending is intended to create additional capability. Otherwise routine maintenance gets presented as an optional investment until something important stops working.

The following examples are proposals for discussion, not recommended ratios for every company. A CFO or accountant would adapt the categories and treatment to the actual business. The purpose is to demonstrate how different operating models lead to different allocations.

Then give department owners an actual spending plan.

This second example is a separate hypothetical service business with a $3 million annual operating-cost plan. It is not an additional layer on the $10 million examples. The denominator is total planned operating costs, not revenue. Each dollar appears once, including the payroll, contractors and tools assigned to the cost owner.

This is how I would make a proposed allocation reviewable, not how I would price an unknown company. The central learning line covers separately approved program costs; ordinary salary remains in each person’s home function. A person working across departments is allocated consistently rather than counted at full cost twice.

Each owner should have an approved amount, the assumptions behind it, a spending authority and a forecast. A monthly review should explain material changes and the proposed response. Spending less than budget is not automatically a success if the department failed to deliver essential work.

The plan also needs a distinction between timing and cancellation. An unfilled role may create temporary underspending while leaving a capability gap. A delayed invoice does not create savings. Finance helps the organization see those differences before someone proudly spends the same money a second time.

The organization changes as the business changes.

In a startup, people will hold several responsibilities. The useful discipline is to name them and make priority decisions explicit. The founder may lead sales, product and hiring, but the calendar still has the same number of hours. Early outsourcing can supply specialist depth while preserving an internal owner.

In professional services, capacity, quality review, utilization and knowledge transfer deserve attention. In manufacturing, production, procurement, maintenance, safety and quality have close dependencies. Retail and ecommerce bring merchandising, inventory, fulfillment, returns and customer service into the center of the model. A software subscription business adds continuing product development, reliability, onboarding and retention responsibilities.

A nonprofit needs an organization capable of delivering its mission, managing funds responsibly and sustaining the work. Restricted funding is not interchangeable with unrestricted cash. Program, fundraising and administrative classifications should follow the actual work and applicable accounting rules. A low overhead ratio alone does not establish that an organization is effective.

The IRS discussion of nonprofit governance provides context on responsible oversight for charitable organizations. The exact structure should reflect the entity and its governing requirements. Volunteers and a meaningful mission do not remove the need for clear authority, records and operating support.

Growth should trigger review of the design. A new location, regulated customer group, acquisition or product can create work that the old organization never had to perform. Adding the new responsibility to whoever seems most helpful may solve the first week and create a permanent bottleneck.

Ownership background matters without becoming a management stereotype.

Veteran-owned, service-disabled veteran-owned, minority-owned and women-owned businesses can encounter different networks, opportunities and barriers. The owner’s experience may shape the company’s purpose and relationships. It does not tell you how every person in that category manages, communicates or wants the business to grow.

As a Marine veteran, I understand why service can be meaningful to a founder’s story. I would still begin with the individual business: its capabilities, customers, people, constraints and objectives. My veteran-owned business advisory addresses that commercial work without reducing the company to a label.

Certification and contracting programs require their own investigation. The SBA’s veteran resources and SBA certification information are starting points for current program details, including relevant veteran, women-owned and business-development pathways. Eligibility, ownership, control, size and other conditions must be checked for the specific program. A descriptive identity alone does not establish certification or guarantee a contract.

Minority ownership is not an automatic substitute for the specific eligibility requirements of the 8(a) program or any other procurement program. Federal, state, local and private supplier programs can differ. The operating plan should account for the time, evidence and delivery capability required to pursue an opportunity, with qualified assistance where appropriate.

For women-owned businesses and other ownership groups, access to capital, professional networks and experienced advisors may be important practical topics. Ask the owner which barriers are real in this business. Good advice should expand opportunity while respecting the person’s individual experience and choices.

Review whether the design makes work easier to complete.

Watch the ordinary signals: decisions waiting without an owner, repeated handoff errors, customers explaining the same issue several times, avoidable rework and people carrying responsibilities no longer reflected in their role. These are useful clues before a major reorganization is justified.

My PMP and Certified ScrumMaster background, alongside Kaizen, RUP and Waterfall, encourages a deliberate approach. Establish the problem, map the dependencies and choose a bounded change. Consult the people affected. Give the new arrangement enough support to work and inspect the result rather than assuming the announcement completed the transition.

A dashboard can help if it shows outcomes and context. Consider decision lead time, delivery quality, customer retention, cash forecast variance, internal mobility and critical skill coverage. Avoid making each department optimize a number that harms the whole. My dashboard consulting work starts with the decisions the information should support.

The company should become easier to understand from the inside. People should know what good work looks like, where they have freedom, who can resolve a conflict and how they can grow. That is the standard I would use to judge the organization, even if the boxes on the chart are less symmetrical than everyone originally hoped.

Questions worth discussing before changing the organization.