Before You Start

Project Management for Non-Project Managers – Things To Do Before You Starting Using Your Work Breakdown

A Work Breakdown Structure (WBS) isn’t just a tool for project managers. Whether you’re starting a new project, taking over an existing one, or sponsoring it, understanding the fundamentals helps ensure a smoother, more predictable outcome for your work. You’ve already learned why they’re important, how to build one, and how to validate it. Let’s look at what you need to know before you start using it:

Constraints and Assumptions

Before you create a WBS, ask yourself and your team: What are my limitations? What are my assumptions? If you’re launching a new product, do you already have the facilities, suppliers, or technical expertise needed? If you’re expanding into a new market, what permits, partnerships, or regulatory roadblocks exist? If you’re taking over or joining a project, what decisions have already been made, and what gaps need filling?

If your company has done similar projects before, previous templates, project files, and lessons learned reports can help. If you’re lucky, there may even be formal documentation. If you’re starting from scratch, find templates or examples from similar projects. If you’re comfortable with AI, it can also be helpful.

Scope

Your first step is defining scope and objectives. What does success look like, and what deliverables need to be completed? Identify and engage stakeholders: who cares about or will be impacted by this project, and what are their expectations? Gather requirements, business needs, and understand the power dynamics early to prevent costly changes later. It’s worth spending time here.

Structure

Now you can project into logical chunks. Figure out how you want to organize it:

Phases

Phases organize by time. If you’re doing a home renovation, for example, you could organize it by design, demolition, structural work, interior finishing, and hand-over.

Components

If you’re building a thing you can break it down by parts. An new prototype aircraft could be broken down by its airframe, engine, flight controls, cabin layout, electrical & hydraulics, and of course testing & certification. All the parts, and all the work to assemble and test the parts as a whole.

Functions

Sometimes you need to build an ongoing operation. For a new e-commerce system could be broken down by front-end and customer experience, product and inventory management, fulfillment, payment & security, customer support, and business intelligence & data analytics.

Risks

Identifying risks early is crucial. What could derail the project? Budget cuts? Supply chain issues? Skill gaps? I’ll have more to say in future posts, but it’s worth mentioning now. Managing work means managing cost, time, and quality. Managing those means planning for things to not happen the way you hoped or expected.

Assuming everything will go smoothly all the time is at best naive, at worst negligent and dangerous. Start your list of risks early, update and add to it on a regular basis and as you learn more.

Taking Over an Existing Project

If you’re stepping into a project mid-stream, start by analyzing the project files. Does the WBS match reality, or are tasks missing? Are work packages too vague or too detailed? Have there been major changes, delays, or budget shifts? What are the major risks and how are they being managed? What are the key milestones? What is the critical path?[1] Are there project files?

Look for warning signs like unclear ownership of tasks, deliverables with no due dates, or a WBS that’s not being actively used. If it’s in bad shape, re-validate it with the team and make the necessary adjustments[2] to get it back on track. Those who plan the fight don’t fight the plan.

---

Joining a Project

Even if you’re not the project manager, you still need to understand your role. The best way to get up to speed quickly is to identify the section(s) that applies to your work, figure out who (not what, important distinction) your dependencies are, and get a sense of key milestones and deadlines.

A useful questions to ask is: “What does success look like for the business/organization/larger team?” followed by “What does success look like for me and my team?” Ensure you’re aligned with the overall project goals.

Success here isn’t just about successfully completing your part of the project. It’s also about helping out the team where you can, but especially in making your deliverables on time when others are dependent on your work. Especially especially if you’re on the critical path.

Being a Project Sponsor

As a project sponsor, you may not build the WBS but you need to understand it. Look for clear deliverables tied to business outcomes, major risks and dependencies, and a realistic budget and timeline.

Good questions to ask your project manager include: How confident are we in these timelines? What assumptions could impact success? What is the critical path? What risks are we actively managing?

Watch for a missing or vague WBS, or missing or vague progress measures. If the project seems directionless, it may be a sign that the WBS needs reinforcement.

Making it Work

A WBS isn’t just a bureaucratic document. It’s a blueprint for execution. Whether you’re building one from scratch, fixing a broken one, or using it to oversee a project, a good WBS keeps everyone aligned and accountable.

Define success early. Check assumptions before diving in. Use it continually rather than as a one-time checklist. Adjust when reality doesn’t match the plan. A well-structured WBS makes it easier for everyone, no matter their role, to get things done.

---

[1] A critical path is that part of a schedule which, if it’s delayed by one day, the entire project is delayed by one day. Every project has one and only one critical path. It might change as the plan adjusts, but there is only one. Every competent project manager will know what it is.

[2] A Graybeard Moment™: Don’t know were to start? Start by cleaning things up. Whether you’re rebuilding an old motorcycle, or putting a project plan back to rights, start by inspecting and cleaning everything. Review the WBS and apply the tools you’ve already learned about. Do the same with assumptions, risks, stakeholder analysis, schedule, or anything else that’s in the project files. What needs to be done next will probably be obvious after you’ve done that. More on all those things in later posts…