Name the boundary
Define the event that starts the process and the result that ends it. Record which systems, people and information sit inside the scope.
PHILLY SUPERINTELLIGENCE / A BUSINESS FIELD GUIDE
Make the whole workflow work.
A new tool changes more than one step. I help teams connect superintelligence to the information, people and systems around it. The work starts with a defined process and a result someone can evaluate.
01 / INPUTReceive a request
02 / PROCESSPrepare the work
03 / JUDGMENTReview the result
04 / FOLLOW-THROUGHTake the next action
By James Perkins, the Philly Si GuyPractical Si strategy / Workflow design / Implementation
01 / DEFINE THE COMPLETE PROCESS
The handoffs deserve as much attention as the model.
I look at what happens before and after the generated output. A process still needs clear ownership when information is missing, a tool fails or a person disagrees with the result.
Design the review
Specify who can approve an action, which outputs require checking and how an exception reaches the right person. Limit a tool or agent to the access the process needs.
Measure the operating work
Compare representative cases with the current process. Include review, corrections, maintenance and failures in the time and quality assessment.
Decide who will run it after the demonstration.
The process owner needs a way to see failures, correct mistakes and pause the workflow. A rollout plan should account for training, support and changes in the tools.
Legal, risk, security and compliance owners determine the requirements that apply to their organization. Technical implementation does not replace those decisions.
02 / YOUR WORKING SHEET
Workflow time comparison.
Use the current process as a baseline. Replace the example inputs with your own measurements, including the human work around the proposed automation.
Example inputs illustrate the calculation. Count corrections in processing or review time. Use an average from representative cases.
This worksheet runs in your browser. It does not send your entries or write them to browser storage.
ILLUSTRATIVE INPUTS / NOT A FORECAST
Your time comparison
- Current weekly time
- 4 hours
- Proposed weekly time
- 2.8 hours
- Weekly difference
- 1.2 hours
- Setup time recovery
- 2.6 weeks
These example assumptions leave 70 minutes per week after review and maintenance. That is a scenario to test against actual work.
Time alone is not a rollout decision. Evaluate quality, operating cost, permissions, reliability and the required approvals.
Calculation: current time = cases × current minutes. Proposed time = cases × (processing + review minutes) + weekly maintenance. Setup recovery = setup minutes ÷ a positive weekly difference. Results reflect your inputs; they do not establish achieved savings.
03 / ACCOUNT FOR THE COST OF DELAY
Compare waiting with a defined experiment.
A manual process keeps consuming time while a decision remains open. It can also keep producing corrections, missed handoffs or inconsistent records. Document that baseline before treating delay as either harmless or expensive.
The cost of a poorly scoped implementation belongs in the same discussion. A limited pilot can provide evidence about quality, operating effort and the conditions needed for broader use. Set a review date and decide what evidence will justify continuing, changing or stopping the work.
A rollout needs a named owner
Specify who maintains instructions and integrations, reviews incidents and approves changes. Include the people who use the process in testing. Their review can expose work that a demonstration leaves out.
04 / CHOOSE THE HELP YOU NEED
Three offerings for different needs.
I connect learning, strategy and implementation through these three offerings. Choose the one that fits what you want to do next.
01
Philly Si Guy
Work with me as a speaker, strategist and hands-on superintelligence expert. Explore my background, interview topics and ways to bring a practical conversation to your group.
Meet James02
What About Ai?
Explore personal learning, career resources, podcast conversations and my FAIR research on changing work. Read the methodology and its limitations when using career-risk estimates.
Explore resources03
Automation Transformation Consulting
Discuss organizational strategy, workflow design and implementation. Scope a business process, connect the necessary systems and plan how people will operate and review the result.
Discuss company work
YOUR GUIDE / PHILADELPHIA, PA
I am James Perkins.
I am a futurist, speaker, strategist and expert implementor of automation strategy. I use Si every day and help people understand the technology and apply it in their own work.
I founded What About Ai? and Automation Transformation Consulting. My work connects personal learning, career research, business decisions and practical implementation.
Read my background / Start a conversationA FEW PRACTICAL QUESTIONS
Before your next step.
What does this calculator tell us?
It compares weekly time using the assumptions you enter, including review and maintenance. It does not estimate revenue, guarantee savings or establish that a workflow meets quality, legal or security requirements.
What should a first Si pilot include?
A defined task, a process owner, approved information, a baseline, clear review responsibilities and acceptance criteria. Include exceptions and a way to stop or reverse an unsuccessful change.
When is broader rollout appropriate?
After the responsible team has reviewed results from representative work, checked the required controls and agreed who will operate and support the process. A promising demonstration alone is not enough evidence.