Skip to main content

The Hidden Cost of a Project: Lack of Preplanning

Ariel Kidwell|

Poor internal planning can derail even the best digital projects. Learn how to prepare your team before kickoff.

After years of working with large organizations with complex departmental structures, we’ve learned the importance of the work a client does before an agency like ours kicks off a project. When you start the RFP process for a website design or digital project, you should expect the agency you hire to arrive with a plan you can count on. After all, that expertise is a big part of what you’re paying for. A good agency will chart a recommended course based on its experience and your requirements. But even the strongest plan rests on assumptions about your team’s availability, decision-making, and readiness, and that’s where projects start to drift. Every week lost to slow feedback, unclear ownership, or missing documentation costs you time, budget, or team morale.

The good news is this is preventable with a few key planning items that build a foundation for more efficient work and help your colleagues feel heard and included.

What it looks like when it goes wrong

Poor internal planning rarely causes one dramatic failure. It shows up as a steady accumulation of small delays and pinch points that eventually turn into real costs.

What’s the worst that can happen?

  • Extended review cycles. When reviewers don’t have enough time to respond in the window a phase requires, rounds of feedback stretch out and the schedule slips.
  • Lower-quality feedback. Rushed or last-minute reviews tend to be shallow or contradictory, which leads to unnecessary communication loops and additional work.
  • Late-arriving stakeholders. An important voice joins at the last minute because they weren’t informed of the project and their feedback changes the direction of the whole project.
  • Competing priorities. Other initiatives, such as a reorg, a product launch, or strategic planning, can quietly claim the same people. If no one has planned for that overlap, the creative project is usually what gives.

How does that affect your project?

  • Increases required budget. Extra time spent on project setup, communication, and planning has to come from somewhere, as does time spent chasing and consolidating feedback when your team doesn’t have room in their day to do it.
  • Missed milestones and launch dates. Any of the above can push a deadline, and in a complex organization the launch is often tied to a campaign, a fiscal deadline, or a leadership commitment.
  • Burnout. On a project that runs six months to a year, this one is easy to underestimate. When key team members aren’t given room in their day-to-day work to participate at the level the project demands, they get stretched thin. That leads to timeline drag, weaker feedback, and low morale, and the strain is felt on both sides of the partnership.

None of these are inevitable. Here’s our recommended approach to preparing your organization for a digital project so you can minimize these risks.

1. Tell your organization what’s coming

Create a memo that covers the basics: what the project is, what problem it’s meant to solve, and a general timeline. Then consider who in your organization needs to receive this information. Here is some food for thought:

  • Are there benefits to making it a company-wide notification as an early onboarding tool if multiple departments are going to be involved? Or is it more important that a strategic group of departments receives this email to minimize time-consuming questions early on and unnecessary involvement that could derail the project?
  • What is the best route to deliver this message to ensure it’s actually read?

We’re happy to help you draft a follow-up memo once we’ve onboarded since we can fill in details like timeline, phasing, and specifics around expectations and involvement.

The goal of this step is to ensure the right people are informed early so they can ask questions and flag concerns before they’re asked to review something on a tight deadline.

2. Build your core team, define who should be involved, and determine the decision-maker

In a large organization, it’s difficult to determine who should be in the room and how to prioritize their time. This is an area where we can help, since we’ve seen which departments tend to get overlooked and which stakeholders should at least be informed.

Boots on the Ground

The core team is your executive sponsor plus the individuals who will be involved day-to-day because of their expertise. These are the people we’ll collaborate with most closely and they’ll likely need to dedicate the most time to the project. 

Consulted and Informed

A digital project typically relies on a variety of subject matter experts to come to life. The larger the organization, the more dispersed that knowledge is. Planning early for who these experts are and how they should be involved is paramount. We recommend documenting this as early as possible and socializing this with the involved groups to confirm alignment. It can take the form of a stakeholder map, RACI chart or any other format that makes sense for your organization. It should define which departments are involved and which individuals within those departments should be copied on emails or added to review calls. You may also want to set up an internal review process to facilitate internal conversations to help shape the feedback and ensure it’s comprehensive and consolidated. 

Mapping who is involved at each stage also opens up an important conversation about capacity. Digital projects require real time from our clients’ teams, and it’s best to set that expectation early. That lets you choose the right people and adjust their workloads so they can collaborate with us. When that planning is skipped, participants get frustrated and burned out, and the project slows down because feedback can’t be provided on time.

Having this map early benefits us, too. We can start working with the right stakeholders and get meetings on calendars well in advance.

The Final Say

The decision-maker is the person with the authority to resolve conflicting feedback and make final calls. This person may or may not be part of your core team and is often a member of leadership. We know how valuable that person’s time is, which is exactly why we want to know who they are from kickoff. Once we do, we can get the necessary reviews and meetings on their calendar as early as possible, rather than scrambling for last minute availability.

3. Map your approvals and content needs at the start

Two areas that consistently surprise teams are the time it takes to create content (and facilitate an approvals process) and the time required to obtain legal sign-off.

Content creation

This is the most commonly underestimated piece of a digital project. If your team is handling content internally, it’s a crucial role to fill. Whoever owns it needs adequate time to write, revise, and run approvals. Content has a major impact on both design and development, so ideally it’s complete before wireframing or design begins. Your team members are the best subject matter experts, but it’s worth realistically assessing whether you have the capacity to take this on in-house. If you don’t, we can help source a content strategist to fill that need so your team can just focus on providing feedback and approvals. 

Legal and other approvals

Map out any required sign-offs at the start of the project, and align on who should be involved so we can reserve time on their schedules right away. Depending on your organization, this might also include security reviews, accessibility reviews, brand approval, or vendor onboarding and procurement steps. Including these steps up front also lets us build an accurate timeline and set expectations with the necessary participants so they can plan their schedules accordingly.

4. Start technical discovery and documentation gathering on your side

Discovery is a standard phase of any digital project, but it moves much faster when your team starts gathering information in parallel. This matters most when we’ll be working inside your development environments and DevOps structures. Here’s what to get ready:

  • Documentation. Gather or create the documentation an outside team would need.
    • A diagram of your tech stack
    • An outline of required tools and access documentation
    • Branding and design system files
  • Collaboration partners for design and technical teams. Select a dedicated collaborator for our design and development teams. This makes the work more efficient because you can plan space in their schedule for these conversations, and they build up knowledge of the project over time, so we never have to start from scratch.
  • Code review participants. Select reviewers up front, again with their capacity in mind.
  • Known unknowns and concerns. Outline anything you already suspect this project might affect in your stack or infrastructure, so we can work on solutions together early.

Why this matters

The planning in this post takes real effort, but it’s far cheaper than the alternatives: budget overruns, extended timelines, and a team that’s worn out before the project reaches the finish line. Every hour spent hunting for a stakeholder, waiting on feedback, or reconstructing undocumented systems is an hour not spent on the creative and strategic work you hired us for. Strong internal planning and communication make for a smoother kickoff, and they keep your budget focused on what matters most: design, strategy, and execution – not the daily friction that comes from a lack of preparation.

You don’t have to figure all of this out alone. If you’re preparing for an RFP or a project kickoff, we’re happy to help you build this foundation. To get started, here’s a checklist you can share with your team.

Pre-Kickoff Checklist

Communicate

  • Draft and send a company-wide memo covering what the project is, the problem it solves, and a general timeline
    • Make sure anyone who may touch the project is a priority recipient and knows how to ask questions

People and decisions

  • Name an executive sponsor
  • Identify the core team, including the people involved day to day
  • Identify the final decision-maker and share their availability with your agency partner
  • Create a RACI chart showing departments, individuals, and who is copied on communication or invited to reviews
  • Decide whether you need an internal review process to consolidate feedback and outline who should participate
  • Confirm each participant’s workload can absorb the project and adjust as needed
  • Check for competing initiatives that could pull on the same people

Approvals and content

  • Map required approvals (legal, security, accessibility, brand, procurement) and name who owns each
  • Decide who owns content creation and approval and confirm they have the capacity
    • Decide whether to handle content in-house or bring in a content strategist
    • Aim to have content mapped out before wireframing or design begins

Technical readiness

  • Gather or create documentation of your tech stack, environments, and DevOps processes
  • Name a dedicated technical collaboration partner and confirm their capacity
  • Name code review participants and confirm their capacity
  • List known unknowns, concerns, or constraints so they can be addressed early

 

← Drag →