The first month of a digital project creates evidence about how the work will run. Decisions are either recorded or left open. Access blockers are either escalated or allowed to age. The people doing the work become visible, or senior presenters remain the client’s main point of reference. Early findings challenge the brief, or activity continues without changing anybody’s understanding.
None of these signals guarantees the final outcome. Different projects need different cadences, and early uncertainty is normal. The first 30 days are still a valuable diagnostic because intervention is relatively inexpensive. Expectations are new, scope has not hardened and both client and delivery partner can adjust how they work.
This week-by-week outline is designed for a discovery-led digital engagement. A migration, a pre-scoped build or a live incident response will require different milestones. The underlying tests remain useful: shared decisions, enabled work, visible evidence, managed scope and timely resolution of constraints.
Before day one: make the start possible
Some projects lose their first week before the kick-off. Stakeholders have not reserved time, security requests have not entered the queue, contracts leave responsibilities ambiguous and the client has not appointed an available sponsor.
Prepare a short mobilisation record covering:
- the problem and intended outcome;
- initial scope and explicit exclusions;
- client and supplier roles;
- required people, systems, data and documents;
- security, privacy, compliance and procurement conditions;
- known dependencies and dates; and
- decisions the kick-off must make.
Access does not always need to be provisioned before work begins. The request should have an owner, an appropriate route and a realistic date. Sensitive access must follow the organisation’s controls; urgency is no reason to bypass them.
Confirm which supplier people will attend the start and which will perform the work. The two groups may differ for legitimate reasons. The client should understand the delivery model rather than discover it through unfamiliar names in later artefacts.
Week one: establish decisions and working conditions
A good kick-off creates more than positive energy. Within a short agreed period, both parties should have a written record of:
- scope and assumptions;
- success measures and how they will be evidenced;
- roles, authority and escalation;
- decision and change-control processes;
- immediate actions with owners and dates;
- the discovery schedule; and
- material risks and unresolved questions.
Introduce people through their responsibility. “Sarah is leading the technical assessment and needs the integration documentation by Wednesday” is more useful than “Sarah is part of delivery”. The same clarity applies on the client side. A sponsor, subject specialist and day-to-day project lead have different authority.
Book interviews and working sessions rather than agreeing them in principle. Identify missing participants early. If a senior stakeholder cannot contribute, the sponsor should decide whether a delegate can represent the issue or whether the schedule and risk need to change.
The decision log should distinguish an agreement from a discussion. A friendly summary of the meeting may leave scope, ownership and dates open. Those gaps become expensive once people begin working from different interpretations.
Weeks two and three: produce evidence, not performance
By this stage a discovery team should usually be able to share observations from completed work. The appropriate evidence might include interview patterns, a content sample, an early journey map, a technical dependency, baseline data or a risk that changes the plan.
Observations are not polished conclusions. They show what the team has encountered and how its understanding is developing. For example:
Three stakeholder groups described the same enquiry problem, although they disagree about its cause. We need to observe the current handoff and examine the data before choosing a response.
That is more valuable than a green status label. It exposes a useful tension and names the next evidence.
The source article described a project manager saying work was progressing when none of five planned interviews had happened. “A project that has not started yet, wearing a progress costume” remains a strong description of the failure. Status should report completed evidence, current constraints and decisions needed, not activity language that protects the appearance of momentum.
The client carries responsibility too. In the source example, the agency was criticised for delay while the client had also been slow to provide requested material. Unnamed contribution becomes grievance. Record dependencies and discuss failure on either side while it can still be corrected.
At the end of each week, ask:
- What did we learn that we did not know before?
- Which assumption became stronger or weaker?
- What is blocked, by whom and since when?
- Has the scope changed in substance?
- Which decision is now possible or necessary?
- What evidence should exist by the next review?
Week four: turn discovery into choices
By the end of a first month, a discovery-led engagement should normally have initial findings that affect priorities, scope or approach. The team may still have substantial research to complete. It should be able to show how completed work has advanced the brief.
A useful review includes:
- evidence gathered and its limitations;
- the most consequential findings so far;
- changes to assumptions, risks or dependencies;
- emerging priorities and areas deliberately deferred;
- decisions required, with options and consequences;
- work planned for the next period; and
- any change to scope, cost or timing.
The presence of disagreement can be healthy. Discovery often reveals that stakeholders want incompatible outcomes or that the technical environment constrains the preferred journey. The team should make that tension discussable rather than forcing premature consensus.
If no finding has affected the work, ask why. The project may be simple and well understood. It may also be collecting information without analysing it.
Signals that deserve intervention
Early signals should be interpreted in context. A delayed access request with an approved workaround and an active owner differs from an access problem that nobody has escalated.
No visible evidence from completed work
The team may be blocked, over-producing behind the scenes or managing the narrative. Ask to see working evidence at an appropriate level of maturity. Do not demand polished deliverables simply to prove activity; that can divert the team into presentation.
Essential stakeholders cannot participate
Repeated absence may indicate weak sponsorship, poor timing or an over-broad discovery plan. Confirm which decisions genuinely require that person and use their time carefully. If the project cannot proceed without them, the sponsor needs to resolve the priority conflict.
Access remains unresolved without a safe plan
Identify the precise dependency and the organisation’s control requirements. Escalate through the agreed route. A supplier should not imply that internal security is bureaucracy; the client should not leave a valid request unattended and then hold delivery dates unchanged.
Scope grows through ordinary conversation
Discovery can reveal necessary work outside the initial brief. Record it, assess its effect and make a decision. When three workstreams become six without an explicit choice, the project has already demonstrated weak governance.
The working team is invisible
Clients should know who conducts research, makes design decisions and leads technical work. Suppliers should also be free to organise specialist contributions without turning every participant into a relationship lead. The issue is accountability, continuity and confidence in the people performing material work.
Decisions remain oral
If an important agreement cannot be found later, it will be reconstructed differently by different people. Keep the record proportionate: date, decision, rationale, owner, consequences and any condition for reopening it.
Intervene with specificity and shared responsibility
Early feedback works best when it names an observation and a consequence without assigning motive.
For example:
Three stakeholder sessions remain unconfirmed, which means the team cannot test the service assumptions this week. What is preventing confirmation? I will resolve the internal availability issue; can we agree the revised schedule and impact by Thursday?
This creates a joint problem to solve. If the issue repeats, use the escalation and change process already agreed.
Avoid waiting for a formal monthly review when a material constraint is already visible. Also avoid treating every variation from the plan as failure. Discovery exists partly to change the plan in response to evidence.
The sponsor’s role is to create timely decisions, access and organisational attention. The delivery partner’s role is to surface constraints, show evidence, protect the integrity of the work and explain consequences. Each should be able to challenge the other.
Use the first month as a learning period
Working habits can become harder to change later, though they do not literally calcify after four weeks. Review the operating relationship while there is enough evidence to discuss and enough flexibility to respond.
Ask both sides what should continue, stop or change. Update the decision process, meeting rhythm, evidence expectations and escalation routes. If the first month reveals a fundamental mismatch in scope, team or approach, address it directly rather than relying on later effort to compensate.
The downloadable one-page project sponsor checklist contains the week-by-week expectations, signals and intervention prompts from this article. Use it as a conversation aid rather than a stopwatch. The aim is to recognise drift early, distinguish it from normal discovery uncertainty and make the next decision while it is still comparatively easy.
