When the Assignment Isn't the Problem

A growing service business preparing for franchise expansion needed its 300+ page operations manual ready for prospective franchise partners.

The assignment appeared straightforward: review a nearly finished manual for grammar, readability, and presentation.

It wasn't.

The document had already undergone multiple rounds of internal and external review, but early analysis revealed that substantial portions had been adapted from another company's materials and did not accurately reflect the business, its operating environment, or the information a prospective franchise owner would need.

The challenge quickly shifted from editing a document to determining whether the document was safe, accurate, and usable enough to represent the business at all.

I entered the organization with no experience in the industry and was simultaneously onboarding into a new role and supporting an active franchise pipeline.

Rather than treating that lack of domain knowledge as a disadvantage, I used it deliberately.

The manual was intended to communicate the business to people who did not yet know how it worked. Reading it cold created a real-world simulation: could an experienced businessperson with no knowledge of this particular business understand the operating model from the information provided?

At the same time, the document became an accelerated immersion into the company itself.

The commercial deadline created another constraint. Prospective franchise partners were already moving through the pipeline. The company needed a viable V1 quickly.

Perfection could wait.

Material inaccuracies, unnecessary risk, and fundamental gaps could not.

The initial review surfaced anomalies that warranted deeper investigation, including processes that appeared unrelated to the company's business and repeated references to a foreign regulatory environment.

Rather than assuming either the document or my understanding was wrong, I investigated.

Once the source of those discrepancies became clear, I recognized that the original review methodology was no longer sufficient. Material I had already read needed to be reconsidered through a different lens.

I redesigned the project around a deeper diagnostic review.

Every section was evaluated for applicability, accuracy, completeness, clarity, operational relevance, audience impact, and potential business or reputational risk. Where specialized concerns emerged, I used AI-assisted research to rapidly investigate and validate them before making recommendations.

The analysis ultimately produced more than 200 findings.

But 200 comments are not an executive decision-making tool.

I grouped related findings, separated routine corrections from issues requiring leadership judgment, and prioritized the most consequential concerns. Using AI to accelerate synthesis and organization, I converted the analysis into approximately 25 decision areas for a focused working session with the COO/Owner.

The prioritized analysis became the architecture for a collaborative executive review.

Rather than asking leadership to work through hundreds of individual comments, we addressed the highest-risk and highest-impact questions first, using the underlying document as supporting evidence when necessary.

Decisions were captured in real time and translated directly into implementation.

I then reconstructed the manual against that direction: removing roughly 50 pages of irrelevant material, correcting substantive errors, reshaping sections, adjusting language that communicated poorly or created unnecessary risk, filling critical gaps, and preserving material that genuinely served the intended audience.

The result was a substantially leaner, company-specific V1 that could move forward with the franchise initiative.

The original grammar and punctuation review?

That was still waiting for the next round.

Within approximately two weeks, while simultaneously onboarding and supporting other franchise-related work:

• Identified 200+ issues in a 300+ page business-critical document previously considered near completion.
• Converted those findings into ~25 prioritized executive decision areas.
• Removed approximately 50 pages of irrelevant or inapplicable material.
• Produced a reconstructed ~250-page V1 aligned more closely with the company's actual operations and intended audience.
• Reduced material business and reputational risk before the document reached prospective franchise partners.
• Accelerated my own domain knowledge sufficiently to support broader operational work inside the organization.

What began as a copyediting assignment became an exercise in rapid organizational discovery, executive decision support, risk identification, knowledge architecture, and implementation.

The assignment is not always the problem.

Sometimes the most valuable thing you can do when someone asks you to execute is first determine whether executing what they asked for will actually produce the outcome they need.

And sometimes not knowing the business yet is an advantage.

A fresh perspective can expose assumptions that familiarity makes invisible—provided you have the judgment to distinguish “I don't understand this yet” from “this doesn't make sense.”

AI made the work faster. It helped accelerate research, synthesis, and the conversion of hundreds of findings into something leadership could act on.

But it did not identify the problem.

Judgment did.