Skip to content
Interface language: English
Imperium / Signal

Fast, tailored and at scale: when promises demand conflicting ways of working

Test whether a company's promises fit the way it works: connected activities, exceptions, service variants and the consequences of a new scope.

Article language: English

Concept illustration: a woman rests her hands on the outer two of three round discs mounted on an axis in a navy and red interior.
In this article

Description: Test whether a company's promises fit the way it works: connected activities, exceptions, service variants and the consequences of a new scope.

A company promises fast delivery, complete tailoring and the ability to handle many orders. Each sentence sounds reasonable on its own. Only during planning does the conflict appear: individual consultations interrupt shared specialists, urgent orders break up batches, and more clients wait for the same decision. The team must deliver three promises with one calendar.

This does not mean speed, scale and tailoring can never coexist. They need a way to work together: ready-made elements, a clearly defined scope for individualisation, suitable resources and limits on exceptions. Strategic fit is tested in the relationship between everyday activities. A claim of flexibility does not yet answer what to do with an order that requires the arrangement to change.

Which activities support each promise?

In a fictional example, a studio prepares materials for manufacturers. Its standard option uses an approved layout, a defined content scope and a shared review date. The tailored option starts by examining how the material will be used and requires separate decisions. Trouble begins when the standard option starts to include any change and an immediate response without a change in how the work is organised.

Write the promise as an event for the client. “Fast” must have a starting point and an outcome: an answer to an enquiry, a first draft or completion of the whole job. “Tailored” may mean choosing ready-made elements or designing the way of working from scratch. Those meanings require different activities. Explain them before arguing about the appeal of the adjectives.

Harvard Business School describes fit across the value chain as activities connecting with and reinforcing each other. It distinguishes excellence in individual activities from the way they are combined in a strategy. For our studio, the question is whether intake, preparation, review and handover form a system that supports the same promise.

For the standard option, prior approval of a layout can reduce the need to redesign it each time. Clear input requirements help prepare a package for a shared review. An agreed correction process makes acceptance easier to schedule. If the salesperson promises unlimited changes after every stage, they change the dependencies on which the deadline relied.

Not every new request violates the strategy. A product-name change may fit an existing layout. A change to an approval process involving several departments may create a different assignment. Show the difference with a concrete example. The team can then recognise what fits the existing model and what needs a separate proposal.

In the article on strategic scenarios (in Polish), we change external conditions and ask about a plan. Here we leave the environment unchanged for a moment. We examine whether the company's promises and its way of delivering them already fit today. That is a different uncertainty from predicting how a future market will buy.

Where does a new promise change everyone else's work?

Trace one order from intake to use of the result. For each activity record the information, person and decision needed. Then add a new promise, such as an urgent individual consultation in the standard option. Do not assess it only by the meeting's length. Look at preparation, decisions afterwards and the effect on reviews already scheduled.

In the example, the consultation may require the same expert who approves materials for the whole batch. If it appears suddenly, other work waits. This does not prove consultations should be eliminated. It shows that their availability and scheduling should match the service model. Otherwise a promise to one client changes everyone else's deadlines without an explicit decision.

Identifying priorities with a limited team (in Polish) helps reveal availability. Fit between activities goes further: it asks why different work types continually compete for the same resource and whether the company wants to keep that arrangement. A ranking of urgency alone does not repair a model that regularly produces conflicting expectations.

Record activities that help each other too. A good input package can make production and acceptance easier. A clear option name can reduce unsuitable questions before purchase. An approved set of elements can allow some tailoring without designing everything again. The analysis should not end as a collection of conflicts alone.

In the abstract of Aligning Entrepreneurial Strategy, Wright and Miller distinguish fit with the environment from internal alignment of goals and actions. They describe research on scaling software companies and an experiment on evaluating new opportunities. This is a 2025 working paper, not evidence of the cause of every difficulty in a service studio. The distinction nevertheless helps ask whether an attractive opportunity fits the way work is delivered.

If departments are in conflict, framing a shared problem (in Polish) can help. Do not stop at accusing sales of promising everything and delivery of blocking everything. Show the decision and its effect across the whole journey. In our example the question is: in which option can consultation be available without disrupting the other commitments?

Can different goals be combined another way?

Before abandoning a feature, check what it means to the client. They may want a quick answer about whether the task fits the service, not immediate completion of the whole job. They may need tailored content in a fixed layout, not a system built from scratch. Understanding the need more precisely can matter more than choosing which adjective to delete.

In its description of Democratic Design, IKEA presents the joint consideration of form, function, quality, environmental aspects and price. This is a statement of its own product-design approach. It does not prove the results of a particular B2B service. It does show that several goals must be translated into design decisions and a balance between them, rather than treating the number of goals itself as a contradiction.

Aeneia conceptual photography

Our studio could separate a stable foundation from the space for change. The client chooses a layout from an approved set, and the studio develops its content within agreed limits. An unusual approval process goes into a discovery option. This still needs testing, but at least explains how tailoring and predictability are meant to coexist.

Deadlines can be separated too. Quickly qualifying an enquiry need not promise equally quick completion of a tailored project. The website should state what the client receives in the first phase and what information determines the later plan. Otherwise a quick response may be read as the deadline for the whole delivery.

When separating options, check whether the client understands the choice and whether the team applies the same boundary. If the client buys standard but the salesperson removes every limit in conversation, the distinction exists only in the price list. If the delivery team directs every exception to a tailored project even though it fits the approved scope, the boundary is not working properly either.

Walk through the new version using several appropriately prepared cases. What happens to a standard content change, a request for another layout and an urgent consultation? Name the person doing the work, the decision needed and the effect on other commitments. Do not treat the model as tested merely because everyone agreed in a meeting.

What should you do with an attractive exception?

An exception can be a deliberate experiment, but it needs its own basis. Define what the company wants to learn, what it will allocate to the trial and what it will tell other people whose work changes. Do not present exceptional support as a permanent standard if it depends on the owner's ad hoc availability.

When deciding whether to prepare a proposal (in Polish), check not only whether one request can be fulfilled but whether it fits the current model. A company may be able to do a job and still not want to repeat that work as part of its main service. That requires an explanation, not automatic acceptance or rejection.

If a client will help develop a new option, agree service co-creation (in Polish) as a separate scope. It will require time, access to the right tasks and a decision after the trials. Do not let one request quietly rebuild the whole offer before the company checks whether it can sustain the new way of working.

Assess the number of exceptions of the same kind too. A recurring need may justify a new option. It may also result from an unclear description of the standard. Before changing the service, see where customers get their expectation. If the website says “complete tailoring without limits”, the problem may start well before one enquiry is classified incorrectly.

Do not compare revenue from an exception only with zero. Compare it with the work it displaces and the dependencies it creates as well. The company can deliberately choose that investment. Record the reason so that the next salesperson does not treat one special project as proof of the ordinary offer.

Compare two concrete arrangements for the same order. In the first, consultation interrupts the next shared review. In the second, the client chooses from separately prepared time slots and supplies required material in advance. Record what the client receives, who prepares it and which other matters wait. Only that description allows you to assess whether the second option really retains the benefit the client needed.

Do not treat separate options as a cost-free answer. Two routes may need separate materials, pricing and enquiry routing. If they still rely on the same expert without a separate plan for her involvement, the conflict may remain. New names organise the offer only when they correspond to a real way of delivering it.

Also decide who assesses a departure and on what basis. Sales should know when it can confirm a standard change and when another decision is needed. Delivery staff should recognise what has already been agreed with the client. If both sides negotiate the meaning of the option internally every time, the cost of that ambiguity becomes a permanent part of the service.

After several more cases, check whether the reasons for departures recur. Keep their context instead of counting exceptions alone. One major change in the approval model may have a different effect from several small corrections within an approved layout. This informs the next decision about working methods without automatically concluding that the company should accept more or fewer individual assignments.

How do you present a coherent choice on the website?

Set the model first, then write the promise. The site should explain who an option is for, what outcome it covers and what the deadline depends on. If individual discovery is a separate phase, show its purpose. If the standard needs prepared materials, state that condition where the customer assesses whether to buy.

You need not publish the whole internal work map. The client needs to understand the consequences for them. Rather than explain the expert's queue, state how consultations are scheduled and what the review covers. Rather than promise any change, show which elements can actually be tailored. Specifics let the customer assess the service without guessing internal constraints.

Aeneia Design can help translate approved options and their boundaries into site structure, offer copy and the enquiry journey. The decision about how the company works remains with the company. The website should honestly show that choice and help the customer recognise the right scope.

Before publishing a new claim, walk through one ordinary order and one exception. If everyone understands what they do, what they confirm and when scope changes, the promise has a basis for further testing. If everything depends on the team somehow adapting again, change the model first. The word “flexible” has remarkably few hours in a calendar.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear