4.2: Plan of Attack

  ↵

Plan of Attack: From Charter to Architecture

C-Bay is entering the loan services industry with an ambitious franchise-based growth strategy. Your team is responsible for defining what this expansion looks like—strategically, operationally, and structurally. This milestone is your opportunity to act like a professional project consultant: mapping the business case, defining the project architecture, and delivering stakeholder-ready documentation.

You’ll work in five structured phases:

Step 1: Create a Professional Project Charter

Your first task in this milestone is to create a formal Project Charter that defines the purpose, boundaries, leadership structure, and success criteria of C-Bay’s new loan services franchise initiative.

Treat this like a real stakeholder-facing document. You are not just setting up a school project—you are documenting a multi-million-dollar business expansion that will be reviewed by sponsors, partners, and internal teams.

Use the following structure and prompts to guide your writing:

1. Stakeholders

List the individuals and groups with a direct or supporting role in the project. Be specific.
Include the project sponsor, executive decision-makers, your internal delivery team, vendors (if applicable), and the intended franchise owners.

Example: C-Bay VP of Business Expansion, Franchise Operations Manager, Project Manager, Legal & Compliance Team, Real Estate Brokers (franchisees)

2. Problem Statement

Write 2–3 sentences explaining the market gap or challenge C-Bay is trying to solve with this initiative.

Example prompt: C-Bay’s current revenue model depends solely on internal real estate auctions. The company has no presence in the loan origination space, leaving value on the table.

3. Alignment with Business Goals

Explain how this project supports C-Bay’s growth strategy. Focus on quantifiable and strategic targets.

Example: This project will help C-Bay diversify its service offerings, create recurring revenue through franchise operations, and expand brand presence into untapped loan services markets.

4. Project Scope

Clearly define what your team will build, plan, or deliver. Include 3–5 core deliverables or areas of responsibility.

Also name 1–2 major things that are out of scope (e.g., regulatory filings, internal lending software development).

In-scope: Franchise playbook, onboarding system, partner CRM guide.
Out-of-scope: Licensing of loan software, full legal contracting.

5. Constraints

List known limitations that shape your plan—time, cost, staffing, legal, or tools. Think practically.

Example: Must be ready to support 1,000+ franchises in Year 1; only 12 weeks available for planning before launch; must integrate with current C-Bay systems.

6. Success Criteria

Describe how you will measure project success. Include both hard (quantitative) and soft (qualitative) criteria.

Example: System must enable franchisees to generate $1M/year; delivery process must scale past 1,000 locations without rework; playbook must pass stakeholder review.

7. Project Processes

Summarize how your team will organize, validate quality, and manage change.

Example: Weekly checkpoints with sponsor; agile iterations for playbook drafts; use of change log to track scope modifications.

8. Team & Structure

Define who is doing what. Include project manager, research leads, architecture designers, etc.
You may also describe your delivery team structure (e.g., pods, functional leads, centralized model).

9. High-Level Deliverables

List 3–5 major outputs that your team will produce.

Example: Executive Summary, Project Definition and Architecture, Cost Model, Franchise Setup Timeline.

10. Deliverables To / Requested From

Specify who needs to approve your deliverables, and who you may need support or data from to complete them.

Deliverables to: Steering Committee, VP of Franchise Development
Requested from: Finance (cost data), Legal (franchise template), Tech (onboarding systems)

11. Sign-Off

Leave a section at the bottom of your document for sponsor approval.
Use clear titles and placeholders like:

• Approved by:

• Name/Title:

• Date:

This may be simulated in your submission or used for peer/instructor sign-off.

---

When your Project Charter is complete, save and submit it with the filename:
CBay_ProjectCharter_TeamX.docx

 

Step 2: Write the Executive Summary

Now that your team has scoped the franchise planning project, it’s time to translate that scope into a professional Executive Summary. This is your opportunity to clearly communicate the project’s purpose, planning strategy, and business value to stakeholders who may not review every detail of your documentation.

Think of this summary as a high-level leadership brief. It should be concise, strategic, and persuasive—something the C-Bay COO could present to investors or internal leadership.

Your Executive Summary should include the following sections:

1. Overview and Purpose

Open with 3–4 sentences describing what the project is and what this summary includes.

Example: “This document presents a strategic plan to launch a scalable, turnkey franchise system offering loan services to C-Bay’s partner brokers and real estate agents. It outlines the project mission, scope, delivery model, risk posture, and success criteria.”

2. Project Mission

State the mission of the project in one clear sentence.

“The mission of this project is to develop and deliver a repeatable franchise system that enables real estate brokers and agents to generate $1M per year in loan services revenue.”

3. Background and Strategic Context

Explain why this project matters now. Link to C-Bay’s business growth and market opportunity.

Mention facts like: C-Bay generated $108.8M last year, yet has not penetrated the loan services sector; expansion will diversify income and meet unmet customer needs.

4. Objectives and Value

List the project’s core objectives across 5 categories:

• Quality: Meet compliance, usability, and documentation standards

• Scope: Deliver full franchise playbook, onboarding guide, support structure

• Schedule: Launch within 10–12 weeks to align with market window

• Team Dynamics: Efficient use of distributed team with vendor support

• Budget: Deliver scalable model under per-unit cost targets

For each, add a bullet with its strategic value to C-Bay.

5. Completion Criteria

Define how you’ll know the project is “done.” Include 3–5 measurable milestones:

• All franchise setup documentation delivered

• Pilot location launched and operating

• Operational systems approved by legal and franchise ops

• No critical blockers or open issues at sign-off

6. Assumptions and Constraints

List the major assumptions your plan depends on—e.g., internal system readiness, vendor availability, timeline support.
Then list any known constraints or boundaries (e.g., cost must stay within 5% of plan, timeline within ±2 weeks).

7. Stakeholders

Finish with a brief list of who this plan is for:

• C-Bay COO and Franchise Steering Committee

• Franchise Operations and Legal

• Your internal planning and delivery team

---

When complete, your Executive Summary should stand on its own—meaning it can be read and understood without needing to reference the full plan. Use clear, executive-ready formatting and keep the length to one page.

🗂 File name: CBay_ExecutiveSummary_TeamX.docx

🔹 Step 3: Build the Project Definition and Approach

This is the core of your planning milestone. In this section, you will document:

• What the franchise package includes

• How C-Bay will deliver the system

• What assumptions or risks shape your design

• How scaling will work across 1,000+ franchises

But before you can define this, you must understand the business systems involved. That’s why we’re including a guided instructional section in this chapter to teach the following foundations:

🧠 Instructional Mini-Guides: (Research)

1. How the Real Estate Industry Works

   • Broker roles, regulations, and regional variability

2. How Buying and Selling a Home Works

   • Steps in a transaction; software and legal process

3. How Loan Processing Works

   • Origination, underwriting, approval, closing, money flow

4. How Franchising Works

   • Franchise law, systems, support, and scale

Your team should divide up research, learn from the guide(s), and then reconvene to define the C-Bay franchise project structure.

Writing Project Definition and Approach

our Project Charter and Executive Summary outlined what C-Bay intends to do. Now it’s time to define how you will structure, manage, and deliver this initiative in a repeatable way.

In this step, your team will author a professional-grade Project Definition and Approach document. This becomes the working playbook for internal project teams, external vendors, and the leadership team overseeing C-Bay’s expansion.

Each section below mirrors what professionals include in internal plans and PMO briefings. Follow each prompt and think of this like a document that franchise partners and delivery teams will actually use.

✅ What to Include in Project Definition and Approach

1. Project Scope

A. What This Project Will Deliver (Planning Deliverables)

This section provides guidance on how to define the scope of the franchise planning project. The focus is not on building or launching a franchise system, but on developing the planning documentation and frameworks that would enable future implementation.

Start with 1–2 paragraphs that explain what the franchise project covers from a planning perspective.

Separate into:
- Product scope: Define what the future franchise system will include at a high level (e.g., CRM, compliance tools, branding assets). Your role is to outline what should be included—not to develop it.
- Project management scope: Describe what your team is producing to support this vision (e.g., project plan, documentation, architecture concepts, risk register).

Use bullet points to clearly outline what areas are being addressed and where boundaries are drawn.

B. What This Project Will NOT Deliver

To avoid misalignment, specify what is not part of this planning effort. Clarify that your team is not responsible for actual deployment, technical implementation, vendor contracting, legal sign-off, or franchise operations.

C. Context and Team Interactions (Planning Model)

Provide a diagram or narrative that shows how the planning effort connects to the larger franchise rollout process. Include key roles such as:
- Stakeholders (e.g., C-Bay COO, Franchise Operations, Compliance)
- Your Planning Team (authors and coordinators of this plan)
- External implementation teams (who will eventually execute the plan)
- Franchisees (end-users affected by this plan, though not part of planning)

Illustrate the flow of communication, review cycles, and approval checkpoints. This helps clarify ownership during the planning stage.
 

D. Planning Assumptions

List any assumptions required for planning success. These might include access to internal documentation, availability of stakeholder input, or the assumption that the franchise business model will remain stable throughout the planning period.
 

E. Project Management Scope

Explain how the planning process itself will be managed. Describe the use of shared tools, document control systems, team communication methods, and internal review structures. This section should outline how your team will remain coordinated, accountable, and organized throughout the project planning timeline.

2. Project Architecture

This section provides step-by-step instructions for defining the Project Architecture for C-Bay’s franchise planning project. Since you are not building the system, your role is to describe what the system should include, how it should function, and why it is structured this way—based on the realities of franchising, real estate operations, home financing, and loan servicing.

A. Understand the Franchise Business Model

Start by writing a short narrative explaining how C-Bay’s proposed franchise system will work. This should reflect your understanding of what it means to offer a “turnkey” operation for real estate professionals.

Include:

• What components the franchisor (C-Bay) will provide

• How a franchisee will use the system to operate independently

• What systems, support, and infrastructure will be standardized

• The relationship between C-Bay HQ and the local office

B. Analyze the Real Estate Industry Context

Describe how the real estate industry functions and what a typical real estate or loan agent needs to succeed. Address:

• Who the key players are (agents, brokers, clients, lenders)

• The role of a brokerage office in daily operations

• Industry-specific tools, compliance needs, and client services

This section helps define what must be included in the franchise system to support professionals.

C. Understand the Home Buying and Selling Process

Provide an overview of the steps involved in a typical real estate transaction. This will help clarify how loan services integrate into the process.

Include:

• The phases of a transaction (listing → offer → escrow → closing)

• Where clients need guidance

• Points of coordination with lenders, title companies, and appraisers

• Typical pain points or service opportunities

D. Map the Loan Processing Lifecycle

Lay out how a loan progresses from initial application to final approval and funding. This helps define what kind of systems and support tools need to exist in the franchise solution.

Cover the following stages:

• Intake and borrower engagement

• Document collection and verification

• Underwriting and structuring

• Approval, compliance, and funding

Describe which of these stages might be supported by CRM tools, templates, automation, or vendor partnerships.

📁 Submit this section with both a narrative explanation and your conceptual architecture diagram.
This section becomes the structural foundation for your Project Definition and Approach.

3. Project Approach

This section outlines how your team will structure, manage, and execute the planning process for C-Bay’s Franchise Expansion initiative. You are not building the actual system—you are building a strategic plan. Therefore, your approach should show professionalism, coordination, and structure for how the plan will be developed and delivered.

A. Describe the Planning Methodology

Start by describing the overall method your team will use to complete the planning project. For example, will you follow a linear phase-based approach? Will you use agile-style iterations? A hybrid model?

Explain:

• Why this model suits a 10-week planning timeline

• How feedback and revisions are built into your process

• How planning milestones are used to organize progress

• How you adapt if stakeholder feedback or project goals evolve

B. Break Down the Project into Phases

Divide your work into clear, manageable phases. Each phase should have:

• A name

• A goal or deliverable

• A short explanation of what happens in that phase

• How progress is tracked or reviewed

Common phases might include:

1. Research and Discovery

2. Drafting and Outlining

3. Internal Review and Stakeholder Feedback

4. Final Assembly and Submission

C. Explain Team Roles in the Approach

Describe how your team is structured. Don’t use personal names—just functions.

Explain:

• Who is responsible for which tasks

• How leadership is distributed or centralized

• Who coordinates input, feedback, editing, and presentation

Roles might include:

• Planning Lead / Project Manager

• Research and Content Coordinators

• Editors and Document Designers

• Stakeholder Communication Lead (if applicable)

D. Address How Progress Will Be Managed

Show how your team will manage deliverables and deadlines. Include:

• Tools used to track work (e.g., Trello, shared Google Docs, spreadsheets)

• Frequency of status updates (daily sync, weekly reviews)

• How blockers or delays will be handled

• File version control or change-tracking strategies

E. Clarify Stakeholder Engagement in the Planning Process

Describe how and when you will engage stakeholders (real or simulated). This could include:

• Peer review checkpoints

• Instructor/institutional feedback

• Role-played sponsor approval rounds

• Simulated presentation opportunities

Make it clear that your team is not planning in a vacuum. A good project approach includes engagement loops and feedback cycles.

4. Milestones and Deliverables

This section outlines how to define major milestones for your planning project. Milestones are key checkpoints that mark meaningful progress. They are not day-to-day tasks—each milestone represents a completed phase, major deliverable, or key review event in your project timeline.

Since your team is building a planning package—not deploying a franchise system—your milestones will reflect planning outputs, approvals, and internal reviews.

A. Define Your Planning Milestones

Identify 6–8 major milestones across your 10-week timeline. Focus on when significant planning outputs are completed, reviewed, or approved.

Examples of planning-related milestones include:

• Completion of the Project Charter

• Architecture Concept Approval

• Risk Register Finalization

• Stakeholder Review or Peer Feedback

• Final Project Plan Submission

Each milestone should be outcome-based and tied to a clear document or decision point—not just a team meeting or task update.

B. Use a Professional Format for Each Milestone

For each milestone, include the following:

• #: The milestone number (e.g., 1, 2, 3…)

• Milestone: A short, clear title

• Originated by: The team role or sub-team that completes the milestone

• For Approval by: The role or simulated stakeholder who will sign off or review

• Completion Criteria: What must be true for the milestone to be marked “done”

C. Sample Format (Planning Context)

Use the following table structure when listing your milestones:

Sample Table for Milestone and Deliverables

#	Milestone	Originated by	For Approval by	Completion Criteria
1	Project Charter Draft	Planning Team	Instructor (Simulated Sponsor)	Internal review complete and formatted
2	Executive Summary Finalized	Content Lead	Instructor or Peer	Summary approved and stakeholder-ready
3	Architecture Overview Approved	Architecture Coordinator	Instructor (Simulated PMO)	Diagram and explanation approved
4	Risk Register Completed	Risk Analyst	Team Lead	All risks and responses documented
5	Stakeholder Engagement Plan	Comms Coordinator	Team Lead	Roles mapped and review timeline confirmed
6	Final Planning Package Submitted	Full Team	Instructor or Evaluator	All deliverables complete and submitted

D. Milestone Writing Tips

• ✅ Use milestone titles that reflect major accomplishments, not small steps.

• ✅ Make completion criteria specific and verifiable (e.g., “sign-off received” or “peer-reviewed”).

• ✅ Use milestones to communicate sequence and structure—they help your reader understand how your planning effort unfolds.

• ✅ Keep the tone professional, as if writing for a stakeholder who will rely on this timeline to monitor progress.

5. Project Team and Structure

his section outlines how your planning team is organized and how you recommend the future execution team be structured to successfully deliver the franchise system. Think of it as a guide to who is doing what—both in your current planning work and in the eventual franchise rollout.

The goal of this section is twofold:

1. To describe the internal structure of your planning team

2. To recommend a clear operational structure for how C-Bay should staff and manage the delivery of the full project

A. Define Your Planning Team Roles

Begin by describing how your team is currently organized. This part focuses on how you are building the plan—not how the franchise system will be built.

Include:

• Internal roles and responsibilities

• Who is leading the project effort

• How tasks are distributed (e.g., research, writing, diagramming, editing)

• How collaboration and accountability are maintained

You may write this as a paragraph or use a bulleted role list. No need to include personal names—focus on roles and responsibilities only.

B. Recommend a Future Project Delivery Structure

Next, define the proposed structure of the execution team that C-Bay would use to build and roll out the franchise system based on your plan.

This team structure should reflect the scale of the project (1,000+ franchises) and the need for operational clarity across roles.

Include:

• Executive Sponsor and Steering Committee

• Program Manager or Franchise Operations Lead

• Functional Leads (e.g., Legal/Compliance, Training, IT/CRM, Marketing)

• Vendor or Technology Partners

• Support and Escalation Teams

Describe how these roles will interact, who has final authority, and how coordination will occur between departments or vendors.

C. Create an Organizational Diagram (Optional but Strongly Recommended)

If possible, include a visual org chart that shows:

• Vertical hierarchy (who reports to whom)

• Lateral relationships (who collaborates or signs off)

• Cross-functional teams (who bridges between areas)

Label all roles clearly and include a caption for your diagram.

D. Describe Handoff Between Planning and Execution Teams

Conclude this section by describing how your planning team will transfer responsibility to the future implementation team. Highlight:

• What documentation will be handed off

• What guidance, if any, should be provided

• What further clarification or support may be required

This transition guidance ensures continuity and shows leadership thinking.

🗂 Submission Format

Submit your completed document as:
CBay_ProjectDefinitionandApprach_TeamX.docx

This document becomes the backbone of your project strategy. Treat it like something real-world stakeholders will read, approve, and use to track your execution.

🔹 Step 5: Prepare Deliverables for Submission

By the end of the milestone, your team will submit:

• ✅ A completed Project Charter

• ✅ A one-page Executive Summary

• ✅ A detailed Project Definition and Approach document

Be sure all files are named using your team name and saved in your shared folder for instructor review.