ROI Case File No.438 'The Rules That One Hundred Twenty People Don't Know'
The Rules That One Hundred Twenty People Don't Know
Chapter 1: The Company's Uneditable Rules
"We need to change our employment regulations, but we can't."
The CEO of Glitz & Glam turned her tablet screen toward us. It displayed a PDF file—fifty-eight pages total. The text was sharp, but not a single character could be edited.
"We operate eight hair salons in the Tokyo metropolitan area. Stylists, assistants, receptionists—120 employees in total. In the beauty industry, working hours and holidays require special handling, making employment regulations the backbone of business operations."
The CEO showed the PDF's table of contents. Employment regulations, wage provisions, childcare and family care leave provisions, harassment prevention provisions—eight internal policy documents totaling approximately 180 pages.
"Last month, we changed our advisory labor consultant. The previous consultant had spent ten years building these policies, but all that was handed over were PDF files. The original Word files apparently existed on the previous consultant's personal PC, but we've been told they were already disposed of."
"So," Claude confirmed, "180 pages of internal policies are frozen in an uneditable state."
"Yes. Our new consultant said the first step is extracting text from the PDFs and converting them to an editable format. We tried OCR, but—"
The CEO showed the OCR output. Tables were broken, paragraph numbers misaligned, and "Article 12" was split into "Article 1 2." Emphasis marks were garbled, and all ruby text had vanished entirely.
"Our only option seems to be retyping everything from scratch, but neither the new consultant nor our staff has time for 180 pages."
"What impact is the inability to update policies having on your operations?" I asked.
The CEO's expression darkened. "This April, the industry guidelines on working hours for beauticians are being revised. We need to amend the working hours and break time provisions in our employment regulations to comply. But since the source data can't be edited, we can't even swap in just the changed sections. The deadline is a month and a half away."
"Furthermore," the CEO continued, "how many of our 120 employees actually understand what's in the employment regulations? Paper copies were distributed three years ago. Subsequent amendments were only posted on a bulletin board. The rules exist, yet nobody knows the contents. That itself is a risk."
This wasn't a technical PDF conversion problem. The internal policies weren't functioning as "living documents"—creation, management, updates, and communication were all disconnected. The entire system needed to be redesigned from the ground up.
Chapter 2: Five Points of Logic
"The temptation is to start with the PDF conversion, but let's widen the view."
Gemini wrote five letters vertically on the whiteboard: L, O, G, I, C. The LOGIC model.
"The LOGIC model," I began, "is a framework for building solutions in five logical stages. Look—observe the current state. Organize—structure the information. Generate—create solutions. Implement—execute. Control—maintain ongoing management. By following these five stages in order, you design a sustainable solution rather than a stopgap fix."
"Why do internal policy issues require a five-stage process?" the CEO asked. "Can't we just convert the PDFs to Word and upload them to the cloud?"
"If you do that," Claude answered gently, "the same problem will occur again in three years. The consultant changes. The file format changes. The administrator leaves. Each time, you start the conversion work all over again. What's needed isn't converting today's PDFs—it's building a system that ensures this problem never recurs."
[Look: Observe the Current State]
"Stage one—Look. Let's start by observing the current situation," I prompted.
"Who are the stakeholders involved with internal policies?" Gemini asked.
The CEO listed them. "First, the advisory labor consultant who drafts and revises the policies. Next, myself and the executive team, who give final approval. The eight store managers who handle labor management based on the policies. And the 120 employees to whom the policies apply."
"What kind of touchpoint does each have with the policies?" Claude probed.
"The consultant revises the policies two or three times a year in response to legal changes. The executive team approves revisions. Store managers are supposed to reference the policies for labor decisions—but in practice, opening the PDF is such a hassle that they usually just call me directly. As for employees, I imagine most haven't read the policies since they were handed a paper copy when they were hired."
"In other words," I summarized, "the policies exist, but among four stakeholder groups, effectively zero have regular access. That's the current state."
[Organize: Structure the Information]
"Stage two—Organize. Structuring the information," Gemini continued.
"Let's organize the 180 pages of policies structurally," Claude proposed. "For each of the eight documents, create an inventory showing the number of articles, last revision date, revision frequency, and reference frequency. This becomes the basis for deciding which documents to migrate first."
The CEO confirmed. "The employment regulations are referenced most frequently and revised most often—two to three times a year. The wage provisions come next, about once a year. The remaining six documents are rarely revised."
"Then," I decided, "prioritize the employment regulations and wage provisions—these two documents. That's roughly seventy pages combined. The remaining six documents at 110 pages can be handled in a second phase."
"Furthermore," Gemini added, "within those seventy pages, identify the specific provisions that need to change for the April legal revision, and start there. Don't convert everything at once—attack the highest-urgency sections first."
[Generate: Create Solutions]
"Stage three—Generate. Designing concrete solutions," I explained.
"There are three approaches for converting from PDF," Claude presented the options. "First, high-accuracy OCR plus manual proofreading—convert with AI-based OCR, then have the consultant verify against the originals. Second, outsource to a specialist firm—commission a company that specializes in digitizing legal documents. Third, have the consultant rewrite from scratch—create new documents from the ground up while referencing the current policies, ensuring compliance with the latest laws."
"Given the month-and-a-half deadline," Gemini analyzed, "the third option carries high risk. Rewriting from scratch requires extensive consistency checks against existing provisions. A combination of the first and second approaches is most realistic—convert with AI OCR first, then commission a specialist to proofread the low-accuracy sections."
"The post-conversion format matters too," I emphasized. "Converting to Word isn't the end. Store the documents in a cloud-based document management tool with version control, access permissions, and revision history tracking. This is the safeguard that prevents the same problem when the next consultant transition occurs."
[Implement: Execute]
"Stage four—Implement. The execution plan," Claude proposed.
"We'll divide this into three phases. Phase 1: convert only the employment regulation provisions affected by the April revision using AI OCR, with the consultant proofreading. Duration: two weeks. Phase 2: migrate the full text of the employment regulations and wage provisions to a cloud document management tool. Duration: one month. Phase 3: migrate the remaining six documents and build a system for communicating policies to all employees. Duration: three months."
"Phase 1 meets the April deadline," Gemini organized. "Phases 2 and onward can proceed without time pressure."
[Control: Maintain Ongoing Management]
"And now the most critical stage—the fifth, Control. The management framework," I said with emphasis.
"The root cause of this problem was that policy management was dependent on individuals," Claude pointed out. "Word files existed only on the previous consultant's personal PC. To ensure this never happens again, establish three rules."
"First," I listed, "all policy originals must reside on the cloud document management tool. No saving to the consultant's local environment. Second, every revision must record the revision date, reason, and approver, with change history saved automatically. Third, conduct an annual audit of all policies to verify compliance with legal changes and employee awareness status."
"These three rules," Gemini concluded, "are the safeguards ensuring that policies remain 'living documents' regardless of consultant changes or system migrations."
Chapter 3: Where Documents Breathe
The CEO studied the five LOGIC stages drawn on the whiteboard.
"I was only thinking about PDF conversion. But conversion is just one part of Implement. Before that, Look to understand the current state, Organize to set priorities, Generate to compare multiple options, and finally Control to build the management framework. Without designing the whole picture, the same thing will happen again."
"The essence of the LOGIC model," I responded, "lies in simultaneously designing both the solution to the immediate problem and the system that prevents recurrence. Look, Organize, and Generate are the solution design. Implement is execution. And Control is the fortress against recurrence. The moment you skip Control, the solution becomes a one-time patch."
"And one more thing," Claude added. "The problem that 120 employees don't know the policy contents is a challenge independent of PDF conversion. After migrating to the cloud tool, build an environment where employees can easily search and browse the provisions relevant to them. Policies shouldn't be locked in a vault—they should be something everyone references as part of daily operations."
The CEO stood and bowed deeply. "Thank you. This week, we'll start by identifying the provisions requiring amendment and testing the AI OCR conversion."
Chapter 4: The Day Rules Belong to Everyone
After she left, Gemini murmured, "The LOGIC model's five stages seem obvious at first glance, but in practice, an extraordinary number of organizations skip the Control stage."
"Indeed," I answered. "People relax once the problem in front of them is solved. The PDF became Word. It's on the cloud. Great, done. But if you start operating without a management framework, within six months you'll have multiple file versions floating around, and within a year no one will know who has the latest one. Control is the force that keeps a solution functioning as a solution. When you embed that force as a system, a single success becomes an organizational habit. That's reproducibility."
Claude added, "And the five LOGIC stages themselves become a thinking pattern applicable to the next challenge. The Look, Organize, Generate, Implement, and Control used for internal policy issues can be applied with the same structure to store operations manuals, customer data management, and beyond. The value of a framework lies not in solving one problem, but in leaving the organization with a method for solving problems."
Outside the window, salon signs were beginning to light up the evening shopping street.
Four months later, a report arrived from Glitz & Glam.
Phase 1 was completed in two weeks as planned. Three employment regulation provisions affected by the April legal revision were amended and filed before the deadline.
In phase 2, the full text of the employment regulations and wage provisions was migrated to a cloud document management tool. AI OCR conversion accuracy was approximately 92%, but consultant proofreading corrected all errors, achieving full alignment with the originals. Automatic change history tracking, access permission settings, and revision approval workflows were all operational.
But the change the CEO highlighted as most significant was employee behavior. When a search function for the employment regulations was implemented on the cloud tool, there were 342 employee accesses in the first month. The most-viewed provisions were "conditions for taking paid leave" and "procedures for prenatal and postnatal leave." Content that employees had previously inquired about by phone to store managers or headquarters was now being self-served.
Labor-related phone inquiries from store managers dropped from a monthly average of forty-eight to eleven. Store managers gained more time to focus on customer service and salon operations.
At the end of the report, the CEO wrote: "We've begun applying the five LOGIC stages not only to policy management but also to organizing our technical training manuals. Look, Organize, Generate, Implement, Control—just following these five steps structures any document management challenge. And above all, not skipping the Control stage. By establishing an annual audit rule, the vagueness of 'someone must be managing it' has disappeared."
The rules that 120 people didn't know now live where all 120 can summon them at their fingertips, anytime.
"Solving the problem in front of you and building a system that prevents recurrence are separate tasks. What the LOGIC model provides are five stages for designing both simultaneously. Look—observe the current state. Organize—structure the information. Generate—create solutions. Implement—execute. And Control—maintain ongoing management. The first four stages solve the problem. But the moment you skip the fifth stage—Control—the solution becomes a one-time patch. By embedding a management framework, a single success becomes an organizational habit—that is the essence of reproducibility in the LOGIC model."
Related Files
