Professional experience brief 04 of 04 · Field decision intelligence
This example comes from Michael’s prior professional work. It is not a Next Concepts client engagement.
90-second storyProperty Performance Playbook
Chapter 1 of 6: The situation
Use ← → keys
We recorded everything—and learned almost nothing
I turned years of activity logs into a system for deciding what to do next.
Field employees logged visits, conversations, events, contacts, materials, and notes. The system proved that activity happened, but retrieving a property’s history was difficult and the information rarely helped decide what to do next.
VisitsEventsSalesReferralsTargetsGeography
Connected byProperty ID→
01Priority properties
02Suggested activity
03Practical daily route
300+ propertiesThe field portfolio needed priorities—not another list of locations.6+ signalsVisits, events, sales, referrals, targets, geography, and portfolio health were connected.
A map still left me with hundreds of choices
Knowing where every property was did not tell me where I should go.
The Module Mapping Tool made the portfolio visible. It still could not tell me which locations needed attention, what activity might help, or how to use a day in the field intentionally.
The team still had to assemble the decision
01Hundreds of possible locations02Activity history trapped in the CRM03No clear next-best action
What I recognized
The activity and the result needed to tell one operating story.
I used the property ID to connect visits, events, sales, referrals, targets, geography, and portfolio health. For the first time, I could compare what we had done with how each property was performing.
I connected history to performance
What existedFragmented activity logsWhat I sawOne property-level storyWhat was neededA priority the field could act on
From history to the next best action
I designed a playbook that ranked, recommended, and routed the work.
The logic identified priority properties, suggested activities based on patterns in the data, and grouped important locations with nearby stops into practical daily routes. New reports could be uploaded later to refresh the recommendations.
See how the playbook worked
01Connect the property story
A common property ID brought activity, performance, referrals, targets, and geography together.
02Find the priority
The tool compared property health with what the employee had already tried and identified where attention was most useful.
03Make the day practical
Priority locations were grouped with nearby properties into routes of roughly a day’s work instead of sending someone across the entire territory.
VisitsEventsSalesReferralsTargetsGeography
Connected byProperty ID→
01Priority properties
02Suggested activity
03Practical daily route
01Rank the properties02Recommend the activity03Build a practical route
The prototype worked. The rollout was interrupted.
The tool reached live use—even though the organization changed before it could scale.
The working live-data prototype generated real property priorities and routes, and I used its output personally. Others reviewed and supported the direction, but organizational reductions ended the role before broader adoption could occur.
What was demonstrated
300+ propertiesThe field portfolio needed priorities—not another list of locations.6+ signalsVisits, events, sales, referrals, targets, geography, and portfolio health were connected.Live-data prototypeThe tool processed real data and generated real property priorities and routes.Repeatable refreshNew activity and sales data could reshape the next set of recommendations.
What this reveals about my work now
A system should guide work—not merely record it.
This brought the earlier projects together: make complexity visible, connect fragmented evidence, and turn information into action. Through Next Concepts, I use that same thinking to help owners understand what their business already knows and decide what should happen next.
