Chapter 10: Project Delivery Methodology

Introduction

You've found clients (Chapter 8) and closed deals (Chapter 9). Now you need to actually deliver.

This is where consultants succeed or fail.

Great sales with poor delivery = angry clients, bad reviews, refund requests.

Great delivery with okay sales = happy clients, referrals, growing practice.

This chapter provides a proven project delivery methodology: - Kickoff & discovery process - Data structure design workshops - Template development workflow - Testing and quality assurance - Training and handoff procedures - Support and maintenance

By the end, you'll have a repeatable process that consistently produces happy clients.

Project Phases Overview

Typical timeline: 3-4 weeks from kickoff to go-live

Week 1: Discovery & Design
├─ Day 1-2: Kickoff meeting
├─ Day 3-4: Document review and data collection
└─ Day 5: Data structure finalization

Week 2-3: Build & Test
├─ Template development (documents 1-10)
├─ Continuous testing with sample data
└─ Client review and feedback

Week 4: Train & Launch
├─ Day 1-2: Training sessions
├─ Day 3: Live data import
├─ Day 4: First production documents
└─ Day 5: Go-live celebration

Week 5: Support & Optimize
└─ Address issues, refinements, stabilization

Adjust timeline based on complexity: - Simple (5 documents, CSV-based): 2 weeks - Standard (10 documents, database): 3-4 weeks - Complex (20+ documents, integrations): 6-8 weeks

Phase 1: Kickoff & Discovery

Goal: Align expectations, gather all information needed to build

Pre-Kickoff Preparation (Day 0)

Send kickoff package email:

Subject: Ready to Get Started! Here's What to Prepare

Hi [Client Name],

Excited to kick off our project this week! To make our kickoff meeting 
as productive as possible, please gather:

1. All current document templates you use
   - Word files, PDFs, whatever format you have

2. Sample data (if available)
   - Excel spreadsheet with student/client/project info
   - CSV export from your current system
   - Even a partial dataset is helpful

3. Examples of generated documents
   - Recent rosters, reports, invoices
   - Helps me see current formatting

4. List of pain points ranked by severity
   - Which documents take longest?
   - Which have most errors?
   - Which are most critical?

See you [Day/Time]!

[Your Name]

Kickoff Meeting Agenda (2-3 hours)

Part 1: Introductions & Expectations (20 minutes)

"Welcome! Let's start with introductions..."

Cover: - Who's who (stakeholders, their roles) - Project goals (what success looks like) - Timeline (when they want to go live) - Communication (how we'll stay in touch)

Set expectations:

"Here's how this will go: - Week 1: We gather everything, design the data structure - Weeks 2-3: I build templates, you review as I go - Week 4: Training and go-live - Week 5: I'm on standby for any issues

You'll need to commit: - 5-10 hours total across 4 weeks - Mostly reviewing my work and answering questions - Available for 2-hour training session Week 4

Sound reasonable?"

Part 2: Document Review (60 minutes)

Go through each document:

"Let's walk through your class roster. Show me: - Current template - How you create it today - Data sources - Common variations - Edge cases or challenges"

For each document, capture: - Purpose (what's it for?) - Audience (who receives it?) - Frequency (how often?) - Data requirements (what fields?) - Conditional logic needed (show/hide sections) - Current pain points (what goes wrong?)

Part 3: Data Structure Workshop (45 minutes)

"Let's talk about your data. What 'things' exist in your business?"

Example dialogue (Homeschool Co-op):

You: "You have Families, right?" Client: "Yes." You: "Each family has multiple Students?" Client: "Correct." You: "And students enroll in Classes?" Client: "Right." You: "So we have three main tables: Families, Students, Classes. And Enrollments is the bridge that connects Students to Classes. Make sense?" Client: "Yes, I see that."

[Draw Entity-Relationship diagram on whiteboard/screen]

"For Families, what information do you need?" Client: "Name, address, email, phone, emergency contact..."

[Document all fields for each table]

Part 4: Success Criteria (15 minutes)

"At the end of this project, what would make you say 'This was worth it'?"

Common success criteria: - Save X hours per week - Zero formatting errors - Professional-looking documents - Easy enough that any staff can use - Reliable and fast

Document these. Reference them at go-live.

Part 5: Next Steps (10 minutes)

"Here's what happens next: 1. I'll finalize the data structure and share it with you for review 2. I'll start building templates, starting with your #1 pain point 3. We'll have a quick check-in Friday to review first template 4. Sound good?"

Post-Kickoff Deliverables

Within 24 hours, send:

Kickoff Summary
Meeting attendees
Key decisions made
Document priority list
Action items (yours and theirs)
Data Structure Document
Entity-Relationship diagram
Field list for each entity
Sample data structure (blank template)
Project Plan
Milestones with dates
Check-in schedule
Training date (tentative)

Client feels: Organized, professional, confident they made right choice

Phase 2: Template Development

Goal: Build all templates, test thoroughly, iterate based on feedback

Development Workflow

For each document:

Step 1: Analyze Requirements (30 minutes) - Review current template - Identify placeholders needed - Map conditional logic - Design loop structures - Sketch layout

Step 2: Build First Draft (2-4 hours) - Create template in Word - Add DataPublisher syntax - Insert sample data - Generate first version

Step 3: Self-Review (30 minutes) - Check all placeholders replaced - Verify conditionals work - Test all loops - Examine formatting - Fix obvious issues

Step 4: Client Review (Ongoing)

Send preview:

Subject: Class Roster Template - First Draft Ready

Hi [Client],

Class roster is ready for your review! Attached:
1. Generated sample (PDF)
2. Template file (Word, if you want to see syntax)

Please review and let me know:
✓ Is layout correct?
✓ All information included?
✓ Formatting professional?
✗ Anything missing or incorrect?

I'll make revisions and send v2 within 24 hours of your feedback.

Thanks!

Step 5: Iterate (1-3 rounds) - Address feedback - Regenerate - Send updated version - Repeat until approved

Step 6: Mark Complete - Client approves - Add to production template library - Document any special notes - Move to next document

Managing Scope Creep

Scenario: Client adds new requirements mid-project

"Actually, can we also add a field for student shirt size?"

Response:

"Absolutely, we can do that. Let me check if it's in scope:

[Review signed proposal]

The proposal includes 10 documents with the data fields we discussed at kickoff. Adding shirt size means: 1. Updating data structure (5 minutes) 2. Updating affected templates (30 minutes) 3. Retesting (15 minutes)

If it's critical, I can add it now at no charge since it's minor.

If you have several more additions like this, we might need a small change order. But one field? No problem."

Guidelines: - Minor changes (<1 hour): Absorb cost, build goodwill - Medium changes (1-3 hours): Case-by-case judgment - Major changes (3+ hours): Change order required

Always stay friendly. Never say "That's not in scope!" harshly.

Quality Checklist (Before Client Review)

For every template, verify:

□ Data Accuracy - All placeholders replaced (no <> visible) - Correct data in all fields - Calculations accurate

□ Conditional Logic - All IF/THEN paths tested - Edge cases handled (empty fields, zero values, nulls) - No logic errors

□ Loops - All items display - No duplicates - Correct sort order - Page breaks appropriate

□ Formatting - Professional appearance - Consistent fonts and sizing - Colors match branding - Page layout correct - Headers/footers proper

□ Images - Photos display correctly - Sizing consistent - Placeholders for missing images - No broken image links

□ Grammar & Spelling - No typos - Proper punctuation - Client's preferred terminology

□ Output - PDF generates correctly - File naming convention followed - Metadata appropriate

Phase 3: Data Integration

Goal: Get client's data into the system

Data Collection

CSV Approach (Simple):

"Please export your current data to Excel and send to me. Here's the structure we need:"

[Provide blank template with column headers]

Students.csv
StudentID | FamilyID | FirstName | LastName | DateOfBirth | Grade | PhotoPath | Allergies

"PhotoPath should be file name only (not full path). We'll put photos in a separate folder."

Database Approach (Complex):

"I'll need access to your database. Can your IT person create a read-only account for me?"

Or: "Let's schedule a time for me to extract the data with your IT person present."

Data Cleaning

Common issues:

Inconsistent formatting
Phone: "555-1234", "(555) 123-4567", "5551234567"
Dates: "1/15/2025", "Jan 15, 2025", "15-Jan-2025"
Solution: Write cleanup scripts, standardize
Missing required fields
Student without family link
Class without teacher
Solution: Flag for client to fix
Duplicate records
Same student entered twice
Solution: Dedupe, confirm with client
Invalid data
Birth date in future
Negative enrollment count
Solution: Validation rules, error report

Data cleaning can take 20-50% of implementation time. Budget accordingly.

Test Data vs. Production Data

Phase 1: Sample data (Week 1-2) - 10-20 records - Covers typical cases - Fast to regenerate

Phase 2: Full dataset (Week 3) - All client's data - Reveals edge cases - Slower generation

Phase 3: Production (Week 4) - Live, current data - Used for real documents - Must be perfect

Never skip testing with full dataset. Sample data hides problems.

Phase 4: Training & Handoff

Goal: Client is confident and competent using the system

Training Session Structure (2 hours)

Part 1: System Overview (15 minutes)

"Let me show you how this works end-to-end..."

[Walk through full workflow]

Update data (if needed)
Open Word, load DataPublisher add-in
Select template
Select data source
Generate document
Review output
Save/print/email

"That's it. Five steps, 2 minutes total."

Part 2: Hands-On Practice (60 minutes)

"Now you try. I'll guide you..."

Exercise 1: Generate single document "Let's create a class roster for Mrs. Smith's class."

[Walk them through]

Exercise 2: Generate batch "Now let's generate rosters for all 6 classes at once."

Exercise 3: Handle common scenarios - Adding a new student mid-semester - Updating allergies - Fixing a typo

Exercise 4: Troubleshooting - "What if photo doesn't show?" - "What if name is misspelled?" - "What if document looks weird?"

Part 3: Advanced Features (Optional, 20 minutes)

If client is technical: - How to update data - How to tweak templates (minor changes) - How to export to PDF vs Word

Part 4: Q&A (25 minutes)

"What questions do you have?"

[Answer everything. Take your time.]

"What scenarios are you worried about?"

[Address concerns. Demonstrate solutions.]

Training Materials to Provide

Quick Reference Guide (1-2 pages, laminated)

GENERATING DOCUMENTS - QUICK STEPS

1. Open Microsoft Word
2. Click DataPublisher tab → Show Task Pane
3. Select template from dropdown
4. Click "Select Data Source" → Choose CSV file
5. Click "Generate Document"
6. Review output
7. Save as PDF or print

COMMON ISSUES:
- Photo missing? Check PhotoPath field in CSV
- Wrong data? Update CSV, regenerate
- Formatting issue? Call [Your Name] at [Phone]

Video Tutorials (5-10 minutes each)
How to generate documents
How to update data
How to troubleshoot common issues
How to export to PDF
FAQ Document

"Q: What if I need to add a new document type? A: Email me the sample and I'll build it. Usually 1-2 day turnaround.

Q: Can I edit the template myself? A: Minor changes (text, formatting) yes. Logic changes, best to have me do it.

Q: What if something breaks? A: Email or call me. If urgent, text me. I respond within 4 hours."

Go-Live Checklist

□ System Setup - DataPublisher installed and configured - All templates loaded - Data imported and verified - Test generation successful

□ Training Complete - All users trained - Questions answered - Confidence level high

□ Documentation Provided - Quick reference guide - Video tutorials - FAQ document - Support contact info

□ Backup Plan - Old templates still available (just in case) - Data backed up - Rollback procedure documented

□ Success Metrics Defined - How we'll measure success - When we'll check in (1 week, 1 month)

□ Celebration! - Acknowledge the achievement - Thank them for partnership - Set up first check-in call

Phase 5: Support & Optimization

Goal: Ensure smooth operation, address issues, refine as needed

First Week Support (Critical)

Daily check-ins:

Day 1 (go-live): "How'd it go today? Any issues or questions?"

Day 2: "Generated any documents yet? Everything working smoothly?"

Day 3: "Quick check-in. All good?"

Days 4-5: "Anything need tweaking before I consider this fully launched?"

Be hyper-responsive first week. Set the tone for support quality.

Issue Triage

Priority 1: System down (respond within 1 hour) - Can't generate any documents - Data completely wrong - Major functionality broken

Priority 2: Major inconvenience (respond within 4 hours) - One template not working - Data issue affecting multiple documents - Formatting significantly off

Priority 3: Minor issue (respond within 24 hours) - Small formatting tweak - Nice-to-have feature request - Question about usage

Priority 4: Enhancement (schedule for next update) - New document request - Process improvement - Non-critical addition

Common Post-Launch Issues

Issue 1: "Photos aren't showing" Cause: File path incorrect or photos not in specified folder Solution: Verify PhotoPath field, ensure photos in right location

Issue 2: "Document looks different than demo" Cause: Using old template or wrong data source Solution: Verify template version, check data source selected

Issue 3: "Generation is slow" Cause: Large batch or big images Solution: Optimize images, generate in smaller batches

Issue 4: "I got an error message" Cause: Various (missing data, syntax error, system issue) Solution: Get exact error message, check logs, troubleshoot

Optimization Opportunities

After 2-4 weeks of use, look for:

Frequent manual edits → Add to template automation
Repeated questions → Update training materials
Workarounds → Fix underlying issue
New document needs → Expansion opportunity

Schedule 30-day review call:

"Now that you've been using this for a month, let's talk about: - What's working great? - What could be better? - What new documents should we add? - Any other pain points we can solve?"

This often leads to additional billable work and strengthens relationship.

Project Management Best Practices

Communication Cadence

Week 1: Daily - Quick updates - Questions answered immediately - High-touch

Weeks 2-3: Every 2-3 days - Send preview for review - Check-in on progress - Medium-touch

Week 4: Daily (training week) - Coordinate training - Final preparations - High-touch

Post-launch: Weekly → Monthly - Week 1: Daily check-ins - Weeks 2-4: Weekly "How's it going?" - Month 2+: Monthly check-in

Documentation as You Go

Maintain project folder:

/ProjectName_Client
  /01_Discovery
    - Kickoff notes
    - Document inventory
    - Data structure diagram
  /02_Templates
    - Template files (.docx)
    - Version history
    - Client feedback
  /03_Data
    - Sample data (CSV)
    - Production data
    - Data dictionary
  /04_Training
    - Training materials
    - Video links
    - Quick reference
  /05_Support
    - Issue log
    - Change requests
    - Optimization notes

Why this matters: - Easy to find things - Reusable for similar clients - Professional if you need to hand off - Evidence if there's ever a dispute

Managing Client Expectations

Under-promise, over-deliver:

"I'll have the first template to you by Friday." [Send it Wednesday]

"Training will take 2-3 hours." [Finish in 90 minutes]

Be transparent about challenges:

"I'm hitting a technical issue with the photo sizing. I'm working on it and will have it solved by tomorrow."

(Don't disappear for 3 days with no updates)

Celebrate wins:

"You just generated 18 rosters in 2 minutes! That used to take 3 hours. Nice!"

Dealing with Difficult Situations

Scenario 1: Client Isn't Responsive

Problem: You need their feedback but they're not replying.

Solution:

Email: "Hi [Client], I have templates ready for your review but haven't heard back. I want to stay on track for our go-live date. Can you review by Friday? If I don't hear from you, I'll assume what I sent is approved and will proceed."

Set deadline. State what you'll do if no response.

Scenario 2: Client Keeps Changing Requirements

Problem: "Actually, can we also add..." over and over.

Solution:

"Happy to add that. Just want to make sure we're still aligned on timeline and scope.

This addition will take [X hours]. Options: 1. I add it now, pushes go-live by 3 days 2. I add it after go-live in a Phase 2 3. It's a change order ($X)

Which would you prefer?"

Make them aware of impact. Let them decide.

Scenario 3: Technical Issue You Can't Solve Immediately

Problem: Something breaks and you don't know why yet.

Solution:

"I'm running into a technical issue with [specific problem]. I'm troubleshooting and will update you by end of day with either a solution or a plan.

In the meantime, you can still use [alternative approach]."

Transparency + timeline + workaround

Scenario 4: Client Isn't Happy with Results

Problem: "This doesn't look like what I expected."

Solution:

"I'm sorry it's not meeting your expectations. Let me understand exactly what you were expecting so I can fix it.

Can you show me: 1. What you expected to see 2. What you're seeing instead 3. Specifically what needs to change

I want to make this right."

Listen. Understand. Fix. Don't get defensive.

Key Takeaways

Project delivery is systematic: - Week 1: Discovery & design - Weeks 2-3: Build & test - Week 4: Train & launch - Week 5+: Support & optimize

Kickoff sets the tone: - Align expectations - Gather all information - Design data structure collaboratively - Define success criteria

Template development is iterative: - Build first draft - Client reviews - Refine based on feedback - Repeat until approved

Training ensures adoption: - Hands-on practice (not just demo) - Provide reference materials - Answer all questions - Be available first week

Support builds loyalty: - Responsive (especially first week) - Proactive (check in regularly) - Solution-oriented (fix problems fast) - Opportunistic (identify expansion needs)

Documentation protects you: - Project folder organized - Decisions documented - Scope clearly defined - Changes tracked

Happy clients refer. Deliver excellently.

Next chapter: Scaling from solo consultant to sustainable practice.

End of Chapter 10

Next: Chapter 11 - From Solo to Sustainable