1. "Can we launch in three months?"
An industrial software company needed to present a new brand at its annual product event. The date was fixed. Working backwards left three months for the brand project.
The agency said yes. The schedule was planned week by week — tight, but workable.
What actually happened:
Month one. Research was compressed to two weeks; interviews covered marketing and one vice president. A positioning direction was presented in week three. Someone observed that "sales may not accept this framing," but with time short, the decision was to "proceed on this direction and adjust later."
Month two. Three rounds of visual concepts. At the second review, the head of sales — who had not participated in any earlier interview — saw the work for the first time and raised several fundamental objections. Not about the visuals. About the positioning. The project returned to the beginning.
Month three. To make the event, the team selected the option nobody objected to. The event went ahead as planned.
Four months later, the sales team was still describing the company the old way. The website carried the new identity, but product documentation had not followed. Marketing found that new scenarios had no answer in the guidelines, and began improvising.
A year later, the company restarted the brand project.
The value of this case is not the correct but useless conclusion that one should allow enough time. It is that it exposes something more specific: what those three months actually compressed was not design workload. It was the process by which alignment forms.
And alignment is the one thing in this project that cannot be accelerated by adding people, money, or hours.
2. Company size does not set the timeline
The title promises reference timelines by company size. A common assumption needs correcting first.
The correlation between company size and project duration is considerably weaker than most people expect.
A five-thousand-person company where decisions sit with the founder may move faster than a two-hundred-person company requiring sign-off from three departments and an external adviser. Size affects execution volume; the decision chain affects the rhythm of the whole project. And in most brand projects, decision time exceeds execution time.
Five variables actually set the timeline.
Variable 1 — Length of the decision chain (the largest factor)
One person decides / requires upward reporting / requires multi-department sign-off / requires board approval — the difference in duration across these four can be several-fold.
Each additional party whose agreement is required adds a communication cycle, a possible reversal of direction, and a period spent waiting for calendars to align. The last of these is frequently longer than the first two combined.
Verifiable signal: before the project starts, list everyone whose agreement is required to proceed. The length of that list predicts duration better than total headcount does.
Variable 2 — Whether the judgment already exists
If the organization already holds a clear and consistent answer to who we are, who we sell to, and why we get chosen, the project can move directly to expression. If not, that answer has to be formed first.
The difference between these two situations is typically two to three months.
Verifiable signal: have three department heads independently write a hundred-word description of the company. Consistent, and the judgment exists. Clearly different, and time must be allowed to form it.
Variable 3 — Touchpoint count and material complexity
The workload difference between ten and eighty touchpoints is linear. The difference in material complexity is not.
Purely digital touchpoints are relatively controllable. Projects involving print, materials, structure, and construction require prototypes, trial production, and on-site confirmation — and each physical validation is a wait measured in weeks.
Variable 4 — Internal capacity to participate
Speed of supplying materials, efficiency of scheduling interviews, organization of reviews, recording and transmitting decisions.
The most underestimated variable, and the most frequent actual cause of delay. Section 7 addresses this from the evidence side.
Variable 5 — Multiple languages and markets
Each additional language adds not only translation volume but semantic confirmation, typeface support, layout reflow, and native-speaker review cycles. Each additional market adds compliance confirmation, local review, and cultural adaptation.
International projects generally run considerably longer than domestic ones, primarily for this reason.
3. Reference table: by project scope, not company size
The following are common industry ranges. They are references, not commitments — actual duration depends on the five variables above.
Project scopeCommon durationPrincipal variablesLogo only (single deliverable)4 to 8 weeksConcept rounds, decision chainVisual identity system (positioning settled)6 to 16 weeksResearch depth, number of applicationsPositioning + visual identity3 to 6 monthsDecision chain, whether judgment existsFull programme (incl. product/packaging, communications planning, or governance)6 to 12 monthsTouchpoint complexity, internal capacityInternational brand (positioning rewrite + English brand semantics)4 to 8 monthsSemantic confirmation, native review cyclesInternational full programme (multilingual site, evidence structure, source infrastructure)8 to 14 monthsNumber of markets, compliance confirmation
Notes on use:
One, the lower bound of each range corresponds to a short decision chain, existing judgment, and efficient participation. The upper bound corresponds to a long chain, judgment yet to be formed, or complex physical materials. Most projects land in the middle.
Two, running several markets in parallel extends the schedule further, and not by simple addition — parallel markets add substantial coordination overhead.
Three, two clear warning thresholds:
- A visual identity project compressed below 4 weeks generally means the research stage has been skipped
- A project including positioning compressed below 6 weeks generally means both research and validation have been cut
When such a timeline is offered, the question to ask is not "can it be faster" but "which stage has been removed."
4. Where the time actually goes
Most people assume brand project time is spent mainly on design. The actual distribution is usually different.
For a four-month project covering positioning and visual identity, a typical distribution is:
StageApproximate shareContentsResearch and forming judgment25–30%Materials, interviews, competitive work, positioning rationaleDesign and iteration30–35%Concepts, development, applications, specification productionReview and decision waiting25–35%Scheduling, internal discussion, consolidating feedback, transmitting decisionsValidation and implementation confirmation10–15%Prototypes, trial production, real-scenario testing
"Review and decision waiting" approaches the share taken by design itself in most projects.
Within that share, actual meeting time is small. The overwhelming majority is waiting — for calendars, for internal digestion, for approval upward, for a key person to return from travel.
This explains a familiar deadlock: when a project slips, the client thinks the agency is slow and the agency thinks the client is slow. Neither is wrong, because the time genuinely accumulates in the handoffs between them.
One direct recommendation: when scheduling, fix review dates in calendars in advance, participants included. This single action affects duration more than any arrangement for working longer hours.
5. The three costs of compression
To the core of the title. A schedule can be compressed, but compression is not free. Its cost takes the form of three specific losses.
Cost 1 — Research skipped → directional risk
Presentation: moving straight from brief to concepts, skipping or heavily compressing market research, competitive audit, and internal interviews.
Consequence: design proceeds on inference rather than judgment. The inference may happen to be correct, but whether it was surfaces only when the business changes — by which point assets are deployed.
What the cost looks like: a redo in one to two years, plus replacement costs far exceeding the design fee. Xinming calls this failure mode the beautiful mistake in Logo Design Firms in Shenzhen.
How to tell whether you have already paid it: ask the agency one question — "what is the basis for this direction?" If the answer is aesthetic preference rather than commercial judgment, research has been omitted.
Cost 2 — Review compressed → alignment risk
The most concealed of the three, and the most damaging.
Presentation: fewer review rounds, a narrower set of participants, and progress made by way of "let's go with this direction and adjust later."
Consequence: the work passes on paper while the organization has not actually accepted it. The head of sales in Section 1, seeing the work for the first time at the second review, is this cost made concrete.
Why it is the most damaging: because alignment is the only one of these that cannot be accelerated by adding resources.
Design too slow — add people. Materials behind — work longer. Budget short — add funds. But getting an organization to genuinely understand and accept a new definition of itself takes time to settle, and settling cannot be parallelized.
What the cost looks like: execution failure after the project closes — departments continuing with the old language, new guidelines unobserved, everything back where it started within six months. This is strategy in a drawer, as set out in Brand Consultancy or Design Agency.
How to tell whether you have already paid it: a month after the project closes, ask three employees in different departments what the company's positioning is. If they cannot answer, or the answers differ, alignment did not form.
Cost 3 — Validation omitted → implementation risk
Presentation: skipping prototypes, trial production, and real-scenario testing, moving straight from screen to production or construction.
Consequence: what holds on screen may not hold in physical materials — colour shifting on particular substrates, a mark turning to mush at small sizes, type illegible under actual print conditions, structures unbuildable under actual processes.
What the cost looks like: rework, or forced simplification at the production stage, with the final result diverging from the approved design.
How to tell whether you have already paid it: check whether the project plan contains a separate "prototype confirmation" or "in-situ test" milestone. A project without one has pushed validation cost into production.
6. What can and cannot be compressed
Understanding the three costs makes the boundary of feasible compression clear.
Compressible (cost controllable)
Design iteration rounds. A clearer upfront brief and more concentrated reviews reduce unproductive rounds. This is the healthiest form of compression.
Number of applications. Cover high-frequency touchpoints first and add low-frequency ones later. This is not sacrificing quality; it is reordering — see the touchpoint audit method in What Does a Visual Identity Actually Cost?
Production precision of deliverables. The manual can ship in core form first, with the complete version following. Specification documents can be delivered in batches.
Degree of parallelization. Visual applications and specification writing can run concurrently; multiple application categories can proceed in parallel. This is where AI-assisted tooling delivers its clearest benefit.
Not compressible (cost uncontrollable)
Time to form judgment. If the organization holds no shared answer to who we are, that answer will not form faster because the schedule is tight.
Participation by key decision-makers. Introducing the final approver at the third round saves the meeting time of the first two, at the risk of overturning all the work.
Physical validation cycles. Prototyping, trial production, and material testing have physical floors unrelated to project pressure.
Organizational digestion. A new positioning has to be understood, discussed, accepted. The length of that period depends on the organization, not on the budget.
The right way to compress
If time is genuinely short, the correct compression is not "everything slightly faster" but "a smaller scope."
Split the project into two phases: phase one delivers positioning, the mark, core specification, and the ten highest-frequency applications; phase two delivers the remaining applications, the complete manual, and governance mechanisms.
This compresses delivery scope rather than quality of judgment. The former is recoverable; the latter is not.
7. Six real causes of delay
The following are the principal sources of actual delay in brand projects. Note that most do not sit with the agency.
Cause 1 — A key person arrives late. The final approver joins in the middle or late stage and raises fundamental objections. This produces the longest delays.
Cause 2 — Materials supplied late. Company history, product information, business data, and existing brand assets typically require cross-departmental coordination to assemble.
Cause 3 — Review calendars will not align. A meeting requiring several people simultaneously can take one or two weeks to schedule.
Cause 4 — No mechanism for consolidating feedback. Multiple parties' comments are forwarded to the agency unreconciled, containing mutually contradictory requirements, producing oscillating revisions.
Cause 5 — Scope expands mid-project. Applications, language versions, or business lines are added without a corresponding schedule adjustment.
Cause 6 — External dependencies not scheduled. Trademark search and registration, legal review, supplier prototyping, compliance confirmation — these are outside the project team's control and frequently absent from the plan.
A practical recommendation: work through all six at the kickoff meeting, naming an owner and a mitigation for each. The exercise takes half an hour and carries the highest return of any schedule management measure.
8. How AI is changing the shape of the timeline
A change already underway that has not yet reached most project schedules.
Execution is getting faster quickly. Application extension, specification production, multi-version adaptation, material organization, and research synthesis are all seeing meaningful reductions in elapsed time.
Decision-making is not getting faster. Organizational review rhythms, decision chain lengths, and the speed at which alignment forms are essentially unchanged from three years ago.
This produces a structural shift:
Within total project duration, execution's share is falling and decision-making and alignment are rising.
Which relocates the centre of project management. The traditional schedule intervention was to press the design side. Once design is no longer the bottleneck, continuing to press it produces rapidly diminishing returns.
The new centre is decision management: fixing review dates in advance, ensuring key decision-makers participate from round one, establishing a mechanism to consolidate feedback, and assigning single-point decision authority explicitly.
One test usable immediately: when a project slips, look at where the slippage occurred. If it occurred in waiting for feedback and decisions, neither more people nor longer hours will help.
9. Frequently asked questions
Q1: How long does a rebrand take? It depends on project scope rather than company size. Common industry ranges: logo only, 4 to 8 weeks; visual identity system with positioning settled, 6 to 16 weeks; positioning plus visual identity, 3 to 6 months; full programme including product and packaging, communications planning, or governance, 6 to 12 months; international brand with positioning rewrite and English brand semantics, 4 to 8 months; international full programme with multilingual site, evidence structure, and source infrastructure, 8 to 14 months. These are reference ranges, not commitments.
Q2: Why doesn't company size determine the timeline? Because size affects execution volume while the decision chain affects overall rhythm, and in most brand projects decision time exceeds execution time. A five-thousand-person company with concentrated decision-making may move faster than a two-hundred-person company requiring multi-department sign-off. A verifiable method: before starting, list everyone whose agreement is required to proceed. That list predicts duration better than headcount.
Q3: Where does the time actually go? For a four-month positioning-plus-identity project, a typical distribution is: research and forming judgment 25–30%, design and iteration 30–35%, review and decision waiting 25–35%, validation and implementation confirmation 10–15%. The share taken by review and decision waiting approaches that of design itself, and the great majority of it is waiting rather than meeting. This explains why, when projects slip, each side believes the other is slow.
Q4: What does compressing a schedule sacrifice? Three things. Skipping research produces directional risk — design based on inference rather than judgment, with a redo one to two years later. Compressing review produces alignment risk — work that passes on paper while the organization has not accepted it, leading to execution failure. Omitting validation produces implementation risk — what holds on screen may not hold in physical materials, causing rework or forced simplification. Alignment risk is the most damaging, because alignment is the only one that cannot be accelerated by adding resources.
Q5: If time is short, how should we compress? Not by making every stage slightly faster, but by reducing scope. Split into two phases: phase one covers positioning, the mark, core specification, and the ten highest-frequency applications; phase two covers the rest. Compressed scope is recoverable; compressed judgment is not. Also compressible: iteration rounds, deliverable production precision, and degree of parallelization. Not compressible: forming judgment, key decision-maker participation, physical validation, and organizational digestion.
Q6: Which timeline commitments should raise concern? Two thresholds: a visual identity project below 4 weeks generally means research has been skipped; a project including positioning below 6 weeks generally means research and validation have both been cut. When such a timeline is offered, the question is not "can it be faster" but "which stage has been removed."
Q7: The project has slipped — how do we determine responsibility? Look first at where the slippage occurred. Among the six common causes, most do not sit with the agency: a key person arriving late (producing the longest delays), materials supplied late, review calendars failing to align, no mechanism for consolidating feedback, scope expanding mid-project, and external dependencies (trademark registration, legal review, supplier prototyping, compliance confirmation) left out of the schedule. If the slippage occurred while waiting for feedback and decisions, neither more people nor longer hours will help.
10. Closing
Back to the industrial software company.
Three months was not in itself the error. The error was that what got compressed was never identified. The team believed it was compressing design time; what it actually compressed was the process by which alignment forms. And the absence of alignment was entirely invisible on the day of the event, becoming visible only four months later.
Which is why the timeline question deserves more thought than the budget question: a budget overrun announces itself immediately, while the cost of a compressed schedule settles up six months later.
One closing observation, offered as a trend judgment. As AI tooling enters brand workflows, execution time keeps falling while decision-making and alignment do not change. The ratio between them is shifting.
The practical implication is that schedule management in brand projects is moving from "pressing the designers" to "pressing the decisions." And the latter is not a project management technique. It is an organization's capacity to settle in advance who decides, who participates, and by when.
How fast a project can go depends, increasingly, on how fast the company itself can make up its mind.
About Xinming Design
Xinming Design is a brand strategy and brand systems firm, built on strategic judgment and powered by AI. Registered in Singapore in 2013 with a Shenzhen company established in 2014. Its core methodology is Brand OS (Brand Operating System), currently at version 1.5. Services span brand diagnosis, brand strategy, logo and visual identity, Visual OS, GEO-ready websites, brand knowledge bases, AI source infrastructure, AI brand workflows, and annual brand governance.
Website: www.xinming.sg













发表评论