Project Management - Client Management

Keeping design work on track, on budget, and on target.

Project management is the operational backbone of client work. It's how promises become deliveries—managing timelines, coordinating resources, tracking progress, and navigating obstacles. Good project management creates the conditions for good design by handling the logistics that would otherwise consume creative energy.

Project Management Fundamentals

The Iron Triangle

Every project balances three constraints:

      Scope
       /\
      /  \
     /    \
    /      \
   /________\
  Time      Cost

Scope: What will be delivered Time: When it will be delivered Cost: What it will cost

These are interdependent. Changing one affects the others. When a client wants more scope, either time or cost must flex. When timeline shrinks, scope or cost must adjust.

The Project Manager Role

For solo practitioners, you're managing yourself:

Setting realistic schedules
Tracking your progress
Communicating status
Solving problems

For teams, you're coordinating others:

Delegating work
Monitoring progress
Removing blockers
Maintaining alignment

Project Phases

Initiation

Starting the project:

Contract signed, deposit received
Kickoff meeting scheduled
Team (internal and client) identified
Project folder and systems set up

Planning

Setting up for success:

Detailed timeline and milestones
Resource allocation
Communication plan
Risk identification

Execution

Doing the work:

Creative process (see Design Process)
Regular check-ins
Progress tracking
Issue resolution

Monitoring

Keeping on track:

Schedule tracking
Budget tracking
Scope management
Quality assurance

Closing

Wrapping up:

Final deliverables
Client sign-off
Final invoicing
Project retrospective
Archive and documentation

Timeline Management

Creating Timelines

Work backwards from deadline:

Final delivery date
Client review time needed
Production time needed
Creation time needed
Discovery and planning time

Add buffer:

Things take longer than expected
Client feedback may be delayed
Build in contingency (10-20%)

Milestone Planning

Break project into checkpoints:

Discovery complete
Strategy approved
Concepts presented
Direction selected
Refinement complete
Final delivery

Each milestone should be:

Clearly defined
Objectively measurable
Tied to approval or deliverable

Gantt Charts and Schedules

Visual timeline tools:

Show tasks and dependencies
Identify critical path
Track progress
Communicate schedule to clients

Tools: Notion, Asana, Monday, Basecamp, simple spreadsheets

Managing Delays

When timeline slips:

Identify early: Track progress against plan.

Communicate promptly: Don't hide delays.

Understand cause: Your delay? Client delay? External factor?

Present options:

Adjust timeline
Reduce scope
Add resources (if applicable)

Document impact: Note causes and consequences.

Scope Management

Scope Creep

The gradual expansion of project requirements:

"While you're at it..."
"One more small thing..."
"Can we also..."

Unchecked scope creep destroys profitability and timelines.

Preventing Scope Creep

Clear initial scope: Precise deliverables in proposal/contract.

Boundaries defined: What's explicitly out of scope.

Change process: How new requests are handled.

Client education: Explain scope dynamics upfront.

Handling Scope Requests

When new requests arise:

Acknowledge: "Great idea, let me think about that."
Assess: Is this within scope or additional?
Respond: If additional, explain impact.
Propose: Change order with timeline/budget adjustment.
Document: Get approval before proceeding.

Trade-Offs

Alternatives to adding scope:

"We could do X instead of Y"
"We could add this to a phase 2"
"We could simplify Z to make room"

Give clients options, not just "no."

Resource Management

For Solo Practitioners

Managing yourself:

Realistic work hours allocation
Buffer between projects
Time for non-project work (admin, marketing)
Energy and capacity awareness

For Teams

Managing others:

Skill matching to tasks
Workload balancing
Availability tracking
Handoffs and coordination

Contractor Management

When bringing in help:

Clear briefs and expectations
Appropriate oversight
Timely feedback
Fair payment

Communication Rhythm

Regular Updates

Establish predictable communication:

Weekly status updates (for longer projects)
Milestone-based updates
End-of-phase summaries

Clients shouldn't have to wonder what's happening.

Status Reports

What to include:

What was completed
What's in progress
What's coming next
Any blockers or concerns
Action items for client

Keep brief—one page or less.

Meeting Cadence

Typical rhythms:

Kickoff meeting (project start)
Phase check-ins (as needed)
Presentation meetings (milestone deliveries)
Ad hoc meetings (as issues arise)

Not every project needs lots of meetings. Match cadence to project complexity.

See Client Communication for communication best practices.

Risk Management

Identifying Risks

Common project risks:

Client delays on feedback
Scope expansion
Stakeholder changes
Technical difficulties
Resource unavailability
Approval bottlenecks

Assessing Risks

For each risk:

Likelihood (high/medium/low)
Impact (high/medium/low)
Mitigation options

Focus on high-likelihood and high-impact risks.

Mitigation Strategies

Prevent: Actions to stop risk from occurring

Clear deadlines in contract for client input
Precise scope definition

Prepare: Actions if risk does occur

Buffer time in schedule
Change order process ready

Monitoring Risks

Throughout project:

Watch for warning signs
Address issues early
Communicate concerns
Adjust plans as needed

Tools and Systems

Project Management Tools

Simple (solo, small projects):

Notion
Trello
Todoist
Spreadsheets

More robust (teams, complex projects):

Asana
Monday
Basecamp
Linear

File Organization

Consistent project structure:

/Project Name
  /01_Admin
    - Contract
    - Brief
    - Timeline
  /02_Research
    - Audit
    - Inspiration
    - Competitive
  /03_Design
    - Concepts
    - Selected Direction
    - Final Files
  /04_Presentations
  /05_Delivered

Time Tracking

If billing hourly or monitoring profitability:

Toggl
Harvest
Clockify
Built-in tools in PM software

Budget Management

Tracking Costs

Monitor spend against budget:

Time spent (even if fixed-fee, for profitability)
External costs (contractors, stock, fonts)
Expenses

Profitability Analysis

For fixed-fee projects:

Budget vs. actual hours
Effective hourly rate
Where time went

Use for future estimating and pricing.

Invoicing

Tied to milestones per contract:

Send promptly when milestone reached
Include payment terms
Follow up on overdue invoices
Pause work if significantly overdue (per contract terms)

Problem Solving

When Things Go Wrong

Problems will arise. Response matters:

Acknowledge: Don't hide or minimize.
Assess: Understand the situation fully.
Communicate: Tell client promptly with clarity.
Solve: Propose solutions, not just problems.
Adjust: Update plans as needed.
Learn: Prevent recurrence.

Escalation

When to raise the stakes:

Problems you can't solve alone
Client relationship at risk
Legal or financial exposure
Ethical concerns

Know when to escalate to stakeholders, lawyers, or walk away.

Project Closure

Final Delivery

Ensure completeness:

All deliverables accounted for
File organization and naming
Formats as agreed
Transfer method appropriate

Client Sign-Off

Get formal acknowledgment:

Deliverables received
Satisfaction with work
Project complete

Protects against later disputes.

Final Invoice

Per contract terms:

Final payment amount
Due date
Payment method
Thank you and wrap-up

Retrospective

Learn from the project:

What went well?
What could improve?
Any process updates?
Lessons for future projects