ROI Case File No.455 'The April Org Chart'
The April Org Chart
Chapter 1: The Distance to April
"The organization changes in April. I want to be ready before then."
Makoto Yamamoto, CEO of TechnoCraft, placed a single org chart on the table as he spoke — two sheets, actually: the current structure and the structure from April onward. The significant difference: the sales division and the procurement division would be separated.
"Since the company was founded, sales and procurement have moved as one. The same person takes the order, handles the sourcing, and manages the customer. The information lives inside one person's head. That worked — until now." Yamamoto traced a finger along an arrow on the chart. "When they separate in April, the customer information the sales team holds won't transfer to procurement. The information severs."
"Where is customer information currently managed?" Claude asked.
"Individual spreadsheets for each rep," Yamamoto answered. "Not shared. Formats differ. When someone is out, no one else can respond. That's caused issues more than once."
"How many weeks until April?" I confirmed.
"Three weeks," Yamamoto said. "I know it might not be enough time. But doing nothing is worse. Tell me where to start."
Three weeks. Gemini looked up at the words. This request also carried an unstated message: there isn't time to build something perfect.
Chapter 2: ICE Reveals the First Move
"This case calls for ICE."
Claude wrote three letters on the whiteboard: I · C · E.
"ICE stands for Impact, Confidence, and Ease — a framework that evaluates initiatives on three axes to determine priority," I explained. "When time is limited and there are multiple options, ICE provides the rationale for what to do first. Three weeks isn't enough time for everything. But it is enough time to clearly separate what belongs in those three weeks from what comes after April."
"What options have been proposed for a sales support system?" I asked Yamamoto.
"Three vendor proposals: Salesforce's small business plan, HubSpot's free plan, and building out an internal Excel template."
"Let's evaluate each through ICE," Gemini said, drawing a three-column table on the whiteboard.
[Impact — What Effect Will Implementation Have on the Organization?]
"Salesforce," Claude assessed, "has the most comprehensive functionality and the strongest long-term impact as an information management foundation. I score: 10."
"HubSpot free plan," Gemini continued, "covers core CRM functionality and is effective for medium-to-long-term information sharing. I score: 8."
"The Excel template," I said, "can be deployed immediately, but won't fully resolve information silo issues. I score: 5."
[Confidence — How Certain Are We of Results Within Three Weeks?]
"This is the fork," Claude emphasized. "Salesforce typically requires four weeks or more for configuration and training after implementation. Entering April with setup incomplete is a real risk. C score: 3."
"HubSpot free plan," Gemini continued, "completes basic configuration in two days. The UI is intuitive enough to start without formal training. Confident that minimum viable information sharing can function within three weeks. C score: 8."
"Excel template," I said, "is usable today. Confidence is maximum. C score: 10. But Impact is low."
[Ease — How Easy Is Implementation?]
"Salesforce's configuration complexity and contract process: E score: 3," Claude assessed. "HubSpot: from registration to productive use in a few hours. E score: 9. Excel: same day. E score: 10."
"Calculating ICE scores," Gemini wrote three numbers.
- Salesforce: I10 × C3 × E3 = 90
- HubSpot free plan: I8 × C8 × E9 = 576
- Excel template: I5 × C10 × E10 = 500
"The numbers are in," I said quietly. "Within the three-week constraint, HubSpot free plan is the clear first priority. Salesforce becomes relevant after April, once data has accumulated and the case for it is stronger."
Yamamoto stared at the numbers. "My instinct said Salesforce. But when you put time in as a variable, the answer changes."
"That's the essence of ICE," Claude replied. "A superior option isn't always the top priority. The framework measures which option fits the current situation best, across three axes. Time, confidence, impact — remove any one of them and the judgment distorts."
Chapter 3: Designing Three Weeks
"Let's build the concrete three-week plan," Gemini proposed.
"Week one: Register for HubSpot free plan and migrate existing customer information. From each rep's spreadsheet, extract the minimum: customer name, owner name, most recent transaction. Prioritize customers with activity in the past six months — not everything at once."
"Let's model the migration priority in ROI Proposal Generator," I suggested. Entering sales contribution by customer and transaction frequency, the data showed that the top twenty accounts represented seventy-eight percent of total revenue.
"Prioritizing those twenty accounts covers eighty percent of the risk. Trying to migrate everything perfectly within three weeks means April arrives with nothing ready. Start with twenty, continue the rest after April — that trade-off is the critical judgment call."
"Week two: Explanations to reps and a trial period. Sales reps who will be in the separated division spend a week practicing looking up customer info in HubSpot. Collect questions to address in week three."
"Week three: Final adjustments and handover documentation. Enter notes for each customer into HubSpot's memo field. Confirm the information-sharing flow with the newly separated procurement team."
Yamamoto looked up from his notes. "This plan isn't perfect."
"It doesn't need to be," I said. "What matters on April 1st is that customer information is somewhere outside the heads of individual reps. What tool it's in is secondary. The important thing is that it exists somewhere accessible."
Chapter 4: The Day the Org Chart Moves
As Yamamoto rose to leave, he said quietly:
"This was my first time using ICE, but — having three axes means you can explain why that's the sequence. With this table, I can discuss why we're starting with HubSpot instead of Salesforce in terms of numbers, not feelings."
"Deciding priorities also protects the decision-maker," I replied. "A decision you can't explain afterward is one that isolates you within an organization. ICE is a tool for preserving the rationale behind the choice."
Outside the window, thin March clouds were drifting. April was almost here.
Five months later, a report arrived from Yamamoto.
The organizational restructuring was met with HubSpot already operational. The top twenty customer records were fully migrated by the end of week two. In the first month after the restructuring, customer response errors during rep absences: zero.
In July, migration from HubSpot to Salesforce began. The customer data accumulated since April smoothed the transition.
Yamamoto's report read: "I was honestly disappointed when told three weeks wasn't enough time for a perfect system. But the decision to start with just the top twenty accounts was what got us through April. ICE was not a tool for finding the perfect choice — it was a tool for finding what was needed right now."
The day the April org chart moved with data behind it.
"Try to build a perfect system in three weeks, and you arrive at April with nothing. What ICE asks is: what choice generates the most value in the current situation? Impact, Confidence, Ease — multiply those three and sometimes the usable option today scores higher than the superior option in the abstract. The correctness of a priority cannot be separated from its context. Only when the constraints of the situation are factored in does judgment become real."
Related Files
Tools Used
- ROI Proposal Generator — Customer data migration prioritization and investment impact modeling
