Topics

Knowledge Creation Laboratory by CRM(xRM)

Implementing a Weekly PDCA Cycle for SoI: A Practical Guide to Automating Plan, Check, and Act with EMOROCO CRM Lite

Hello, this is Matsubara, CRM Evangelist.

"We've implemented a CRM system, and we've accumulated data. But that data isn't being used to inform management decisions."

This condition indicates that the "System of Insight (SoI) is not functioning."

In Arcus Japan's emphasis on the necessity of Systems of Innovation (SoI), the role of each system in the PDCA cycle is clearly defined.

  • SoI (CRM): Policy planning (Plan), analysis and evaluation (Check), consideration of improvement measures (Act)
  • SoE: Execution (Do) for the customer
  • SoR: Obtained data

In other words, CRM (SoI) is responsible for all three parts of the PDCA cycle: Plan, Check, and Act . SoE is only responsible for the "Do" action taken with the customer, while SoI is responsible for all of the Plan, Check, and Act actions before and after.

However, many companies' CRM systems remain merely an "extension of SoR"—simply "recording information"—and do not implement the PDCA cycle.

This article explains a specific design for shortening SoI's PDCA cycle from monthly to weekly and automating Plan, Check, and Act using EMOROCO CRM Lite's workflow and dashboard .


Why is "monthly PDCA" too slow?

The limitations of monthly PDCA

Many small and medium-sized businesses operate on a monthly basis for their sales PDCA cycle. The typical cycle involves compiling data in Excel at the end of the month, reviewing the previous month's performance at a meeting at the beginning of the month, and then deciding on the current month's strategy.

However, this "monthly PDCA" has a fatal flaw.

Problem ①: Information is delayed by one month.

When the fact that "Company A's enthusiasm had cooled" is first reported at the monthly meeting, that information is already 3-4 weeks old. During that time, Company A may have switched to a competitor.

Problem ②: "Check" is written as "Report".

Most of the monthly meetings consist of "reports" on "how things went last month," and no time is spent on "analysis" and "decision-making" regarding "why things happened" and "what should be done next."

Problem 3: The "Act" becomes a mere formality.

If you identify problems on a monthly basis, but the next time you can address them is at next month's meeting, the actions become meaningless. You end up repeating the same problems you had last month.

SoI enables "weekly PDCA".

When CRM functions as a System of Interest (SoI), the PDCA cycle can be run weekly, or even daily in some cases.

SoI, a system that analyzes data and derives business-relevant insights, functions as a "constantly running real-time analysis engine," automatically delivering insights every morning on "who to contact and what to do this week."

[The difference between monthly PDCA and weekly SoI-PDCA]

Monthly PDCA (traditional type):
End of month: Data aggregation in Excel (4-5 hours)
Beginning of the month: Report at the monthly meeting (1-2 hours)
Mid-month: Each person in charge acts based on their "intuition."
→ Up to one month time lag between problem detection and resolution.

Weekly SoI-PDCA (implemented with EMOROCO):
Every morning: Get a 5-minute overview of the entire situation on the dashboard (Plan)
Daily: The person in charge performs follow-up (Do) ← This is handled by SoE.
After each contact: Record emotional temperature and results within 30 seconds (Check)
Real-time: Workflow automatically generates the next task (Act)
Weekly: 15-minute decision-making meetings (to improve plan accuracy)
→ A maximum 7-day cycle from problem identification to resolution.

Designing a SoI-PDCA cycle: Automating each of the "Plan, Check, and Act" stages with EMOROCO.

■ Plan (Policy Planning) — The dashboard shows "Who should do what this week?"

The purpose of the Plan phase is to clarify "the customers, deals, and actions that need to be taken this week." EMOROCO's dashboard will automatically present this information.

[Design your Plan dashboard in 5 minutes every morning]

[Block 1: This Week's Priority Follow-Up List (Planning Insights)]
Conditions: Automatically extract customers who meet any of the following criteria.

A: Emotional temperature "below cool" × More than 14 days since last contact
→ If we don't make contact this week, there's a high risk of them dropping out.

B: Emotional temperature "Hot" × Next action deadline is this week
→ This week is the best time to close a deal.

C: Follow-up task for automated workflow generation due this week
→ Customers the system has determined should "take action this week"

[Block 2: This Month's Landing Forecast (Planning Insights)]
Condition: Automatically calculate the total amount for projects with a probability of success of A x B.
→ You can instantly see "You need another XX yen and XX transactions this month."
→ Used to determine the priority of "which projects to move forward with this week."

[Block 3: Stagnant Issues Requiring Intervention This Week (Planning Insights)]
Conditions: More than 21 days since the last contact × Phase is before "Proposing"
→ Visualize projects that are not currently in progress
→ Realize "a matter that has been neglected"

[Block 4: ICX Change Alert (Planning Insight)]
Conditions: Customers with recorded ICX change signs × More than 7 days since last contact
→ Customers who are showing signs of emotional change but are not being contacted.
→ Proactive measures are needed to address "changes that cannot be put into words."

Simply open this dashboard every morning, and a priority list of "who to do what for this week" will be automatically generated. This eliminates "time spent thinking about what to do" and maximizes "time spent doing."

[Weekly 15-minute decision-making meetings (to improve plan accuracy)]

Monthly 90-minute reporting meetings → Weekly 15-minute decision-making meetings

Agenda (5 minutes each):
① Check this week's red alerts (5 minutes)
Everyone should review the list of people whose "emotional temperature is below cool and who have had no contact for 14 days or more."
→ The person in charge declares the action and it ends.

② This week's forecast and sense of shortfall (5 minutes)
"We need to reach our monthly goal by XX yen. Which projects should we move forward with this week?"
→ The person in charge declares, "We're aiming to close the deal with company XX this week," and that's the end of it.

③ Sharing the results of last week's Act (5 minutes)
Each person will share for one minute: "What we did last week → Results → How we'll incorporate it into our next plan."
→ The team learns the reasons for lost and closed deals.

■ Check (Analysis and Evaluation) — Record "what happened" in 30 seconds and store it immediately.

The purpose of the Check phase is to "accurately record the results of the execution (Do) and transform them into insights that can be used for the next Plan."

EMOROCO's Check is designed for "30 seconds immediately after contact ends."

[Check field update rule 30 seconds after contact]

Items to update after each contact, visit, or meeting (takes 30 seconds to complete):

① Emotional Temperature (Selection): Hot / Warm / Cool / Cold
② Last contact date: Updated to today's date
③ Next action (single line text): Example: "Send quote next week"
④ Next action due date: Example: "2025/06/13"
⑤ Follow hook (single line text):
Example: "The other party is interested in next month's exhibition. Following up before the exhibition would be effective."

The following items will be updated at least once a week:
⑥ ICX change signs (checkbox):
□ Shorter replies □ Less frequent contact
□ Suddenly became more proactive □ Spoke their true feelings
⑦ In case of lost or stalled deal: Reason for lost deal (multiple choice)
Price / Competitive advantage / Timing / Lack of features / Change of person in charge / Other

As these 30-second checks accumulate, the following Check dashboard will begin to function.

[Weekly Check Dashboard Design]

[Check ①: Evaluation of the volume and quality of activity last week]
• Number of contacts last week (by person in charge)
- Percentage of customers whose emotional temperature "increased" after contact
- The percentage of people who set a follow-up action after contact (an indicator of contact quality)

→ Identify "contact that occurred but caused a temperature drop."
→ Identify "customers we haven't been able to contact"

[Pick ②: Weekly summary of reasons for lost deals]
• Distribution of reasons for losing deals this month
Example: "Price 42% / Competitive advantage 33% / Timing 15% / Other factors 10%"
→ Reflect the question, "What are the common characteristics of projects where the competitive advantage is high?" in the plan.

[Check ③: Trends in changes in emotional temperature]
- A list of customers whose emotional temperature has "decreased" compared to last week.
- A list of customers whose emotional temperature has "increased" compared to last week.
→ Customers who have decreased in engagement → Automatically added to next week's Plan priority list
→ Increased customer → Plan the timing for closing and making a proposal.

[Check ④: Follow-up Contact Rate]
- Percentage of customers we have been able to follow up with this month
- Distribution of time periods for "customers who have not been contacted" (30 days or more, 60 days or more, 90 days or more)
→ Customers with no contact for over 90 days → Automatically added to next week's Plan red alert.

■ Act (Considering Improvement Measures) — The workflow automatically generates "What should be done next?"

The objective of the Act phase is to "immediately generate improvement measures to be incorporated into the next Plan, based on the results of the Check (analysis) phase."

EMOROCO's workflow automation automatically executes this action "before the person in charge even thinks about it."

[UK Design Examples of Workflows that Trigger Actions]

[Act 1: Immediate response to a decline in emotional temperature]
Trigger: Emotional temperature is updated to "cool" or "cold".
Act: "[ICX Alert] Mr./Ms. ○○'s emotional temperature is low - follow-up required this week" task
Automatically generated the following day
Content: "Start not with typical sales contact, but with genuine interest."
No hard selling. It starts with a simple "How are you?"

[Act 2: Promoting intervention in stalled projects]
Trigger: 21 days have passed since the last contact × Phase is before "Proposing"
Act: "[Stagnation Alert] Negotiations with Company XX have stalled - please investigate the cause."
Automatically generate tasks
Content: "Check why it stopped."
Is it a change in personnel, a budget freeze, or competitive intervention?
Record the confirmation results in the phase and ICX change indicators.

[Act 3: Immediately implement the successful pattern in the next step]
Trigger: The project phase changed to "Order Received".
Act 1: Task "[Thank you for your order] Send a thank-you message to XX company within 48 hours of receiving the order"
Automatically generated the following day
Act 2: "[Success Pattern Recording] Narratively documenting the hooks that led to securing the order for Company XX"
Tasks will be automatically generated the next day.
Content: "What was the deciding factor in the end? The words used, the angle of the proposal, etc."
Timing—recording this directly impacts future orders."

[Act ④: Immediate learning loop after losing a deal]
Trigger: The deal phase changed to "lost deal".
Act: "[Learning from Lost Deals] Detailed Recording of Reasons for Lost Deals at Company XX and Consideration of Future Plans"
Tasks will be automatically generated the next day.
Content: "In addition to the reasons for losing the deal (multiple choice),
"What would you do if you encountered the same situation again?"
Record it in a narrative memo.
This will become the organization's learning data.

[Act 5: The thank-you cycle after the referral]
Trigger: New customers acquired through referrals have entered the "contract" phase.
Act: "[Referral Thank You] Report of successful transaction and thank you message to Mr./Ms. ○○ (Referrer)"
Tasks will be automatically generated the next day.
Content: "The project you introduced has been successfully completed."
I will provide you with the details and express my heartfelt gratitude.
This report will sow the seeds for the next introduction."

[Act 6: Regular health checkups for all customers]
Trigger: First Monday of the month (scheduled execution)
Act: "[Monthly Health Check] Reviewing the entire customer portfolio for this month"
Automatically generate tasks
Content: Open the full view of the dashboard,
- Check the emotional temperature of top-performing customers in terms of LTV (Lifetime Value).
- Check the list of customers with a follow-up contact rate of less than 50%.
- Check the monthly distribution of reasons for lost deals.
We will incorporate these results into this month's plan.

Weekly SoI-PDCA: "Weekly Operational Design"

From theory to practice: Here's a sample weekly operational schedule using EMOROCO CRM Lite.

[Monday (Morning, 15 minutes): Plan—Set your priorities for this week]
7:30-7:35 Check the red alert list on the dashboard.
7:35-7:40 Check the forecast for this month's landings and any perceived shortfalls.
7:40-7:45 Weekly 15-minute meeting - All responsible parties declare their actions.

[Monday to Friday (30 seconds after each contact): Check - Record the results immediately]
Immediately after each visit, phone call, or email:
Updated emotional temperature, last contact date, next action, and follow-up question.
*This 30-second check will fuel SoI's PDCA engine.

[Real-time (Automatic): Act - The workflow generates the next task]
Each time the field is updated in Check:
→ Decreased emotional temperature → Immediate follow-up task generation
→ Detection of stalled cases → Generation of intervention promotion tasks
→ Orders received/orders lost → Learning record task generation
(Act will operate automatically without the person in charge having to be aware of it.)

[Friday (Morning, 5 minutes): Check & Plan Preparation - Weekly Review]
7:30-7:35 Check the "Check Dashboard for this week"
Customers whose emotional temperature has changed compared to last week
• Distribution of reasons for lost deals this week
Preview of next week's red alert list
→ I took notes on the agenda for Monday's Plan meeting and finished up.

Checklist for Transitioning from Monthly Reporting Meetings to Weekly Decision-Making Meetings

We will verify whether our company's CRM is functioning as a SoI-PDCA cycle.

[Confirmation of the Plan Phase]
□ Is the "List of Customers to Follow Up This Week" automatically displayed on the dashboard?
□ Can the "monthly landing forecast" be instantly determined without manual calculation?
□ Is the weekly meeting structured so that "everyone declares their action plan and the meeting ends within 15 minutes"?

[Check Phase Verification]
□ Have "emotional temperature, last contact date, and next action" been updated within 30 seconds of contact?
□ Is the "reason for losing the deal" recorded using a multiple-choice format, and is the weekly and monthly distribution visible?
□ Can the "follow-up contact rate" be instantly displayed on the dashboard?

[Confirmation of the Act Phase]
□ When emotional temperature drops, are follow-up tasks automatically generated?
□ Is a "learning record task" automatically generated immediately after an order is received or lost?
□ Are alerts automatically being issued for stalled cases (no contact for 21 days or more)?

[Overall confirmation]
□ Has the task of compiling data in Excel for monthly reports been eliminated?
□ Has the meeting time shifted from "time for listening to reports" to "time for making decisions"?
□ Is it a situation where you "understand the reasons behind your success in numbers" rather than just having a "vague feeling that things are going well this month"?

Summary – Five design principles for implementing a weekly PDCA cycle for Systems of Interest (SoI)

Principle ①: Plan is shown by the dashboard as AI.

Instead of the person in charge having to figure out "who to do what for this week," the dashboard automatically presents a priority list. This is how SoI (Insights) contributes to planning.

Principle 2: The check is performed according to the "30 seconds after contact" rule.

The accuracy of the Check phase depends on the "immediacy of recording." Recording immediately after contact maintains the freshness of the information and improves the accuracy of SoI analysis.

Principle 3: Act is automatically executed in the workflow based on the results of Check.

The workflow automatically generates the Act before the person in charge even has a chance to think about "what to do next." Eliminating the burden of human thought is the only way to run the Act cycle on a weekly basis.

Principle 4: Do is the responsibility of SoE, and SoI does not intervene.

The Do phase (actual contact with the customer) is handled by the person in charge (a human). SoI's PDCA cycle "supports" Do, not "replaces" it. By having SoI handle Plan, Check, and Act, the time that can be focused on Do is maximized.

Principle 5: Transform weekly meetings into "decision-making forums."

We will eliminate the monthly 90-minute reporting meetings and replace them with weekly 15-minute decision-making meetings. Since all the information is available on the dashboard, there is no need for "time to listen to reports." Meetings that focus solely on "what to decide this week" will improve the accuracy of the organization's SoI-PDCA cycle week by week.


EMOROCO CRM Lite allows you to build the entire SoI-PDCA design starting today, from just 1,500 yen per user per month.

First, today, create a view that displays a list of customers with an emotional temperature of Cool or lower on the dashboard. The contact you make with the customers displayed there will be the first Plan in your SoI-PDCA cycle.
EMOROCO CRM Lite Product Page


Related article: [DX and CRM Series Part 1: Don't talk about CRM without knowing the "three-tiered structure" of DX - How SoR, SoE, and SoI are changing the design philosophy of management]

Related article: [Is customer data an "asset" or a "liability"? The difference between CRM that simply accumulates data and CRM that actually utilizes it]

Related article: [DX and CRM Series, Part 3: How CRM 4.0 and EMOROCO CRM Lite enable the implementation of SoI]

 

Person who wrote this article
Shinsuke Matsubara

Arcus Japan Representative Director / CRM Consultant
Click here for detailed profile
He has worked as a system engineer, architect, and consultant at Accenture and other companies, an evangelist at Infragistics (Microsoft MVP for Dynamics CRM (now Microsoft MVP for Business Solutions)), and a solutions specialist at Microsoft (in charge of Dynamics CRM products).He currently leads a service team specializing in CRM, supporting CRM implementation and business launches for companies of all sizes.At the same time, he works as a CRM evangelist, spreading the idea of "true" CRM through events and article contributions.
Having learned CRM at Accenture, and having advocated and globally popularized CRM 2.0 (platform-based CRM) at Microsoft, he is a legitimate successor to CRM and the longest-serving active CRM expert (CRM consultant/CRM doctor), having received an award at Worldwide.
Since then, as a leading expert in CRM who advocates CRM 3.0 (Personalized CRM) and CRM 4.0 (Creative CRM), he has been interviewed and received numerous awards both domestically and internationally from publications such as The Wall Street Journal, Newsweek, TIME, WORLDCOM, Mainichi Shimbun (Weekly Economist), and Nippon Cultural Broadcasting. He has also been selected as a representative company of the Kansai business community by "Keizaikai" for four consecutive years.
book:Versatylist - How to become a "1 in 1" talent by age 35

Interview article
For requests for interviews, lectures, etc., please contact us using the contact information below.
TEL +06-6195-7501-XNUMX
Inquiry via form

Articles in the same category