Plant Portals and Campus Email Force a Queue Decision
Decide whether Greenville plant portal tickets and Clemson office emails should share one queue or stay in two.
Blog
Notes on technology leadership.
Short pieces on technology leadership: the plan, the vendors, the spend, and the reporting. Written for the leaders who own that work.
Latest posts
Every post, newest first.
18 posts, 9 to a page, three across.
Plant Output Should Stay Out of the Bank File
Copying plant output into a lender file creates a second record. Keep orders and output in the production system.
Keep Patient Names Out of the Ledger
Decide which patient identifiers may leave a Chapel Hill practice system when billing files move into accounting. A tenant review reads who can open it.
Keep Client Financials Out of Personal Storage
Decide if staff may keep client payroll and pending work in personal storage. An applications assessment inventories the systems.
Act on Profit Before the Books Close
Profit is still trapped in bookkeeping reports when you must hire, freeze headcount, or change prices. Here is what to do before the close.
Staff the Dock From Real Loads, Not a Separate Calendar
Decide whether warehouse labor should follow outbound volume or a calendar that never sees the dock. An applications assessment inventories those systems.
One View of Charts, Coverage, and the Day's Book
A clinic owner can decide if patient charts, insurance files, and the appointment book belong in one view or should stay apart.
When the Yard Log and the Invoice Do Not Agree
Decide which record stands when the yard log and the downtown invoice disagree. A written rule decides, and one view of the totals does not replace it.
Record How Orders Move Before the Plant Veteran Retires
Before a Cleveland County plant veteran retires, record how orders, stock, and invoices actually move through the company.
When the Close Spans Both Carolinas
How a Rock Hill owner closes one month when staff and payroll sit in both Carolinas. Both states have to show before the books are locked.
Map the Plant ERP Before Adding More Software
Map how the original plant ERP works so operations can follow it before you add more production software. The inventory shows tools that already overlap it.
Should Shop Drawings Still Leave as Email Attachments
Decide whether shop drawings and bid packages should still move as ordinary email attachments. An applications inventory shows whether a folder already exists.
Leave Unused Archives Behind When Tenants Change
Owners changing cloud tenants must decide whether every old inbox and archive moves, or only mail and files still in use.
End File Rights When the Production Wraps
Decide if freelance crews retain file rights after a wrap, or if those rights end when the job ends. An inventory lists accounts that still hold copies.
Which Applications Join the Shared Picture
A COO must choose which applications feed one operational picture and which stay on their own. This article shows how to sort them.
Nothing Written Down Before the Next Customer Review
Plant owners near the Charleston port must decide if staff may keep writing specs and pricing vendors on personal AI accounts with nothing written down.
Retire Quiet Systems or Keep Paying for All of Them
Owners and COOs decide which business systems stay in daily use and which get retired so they stop consuming attention. The list is an applications inventory.
The Technology Plan Still Has No Owner
This quarter the owner already knows the plan is split. Spend, vendors, approved tools, and licences need one owner before the next pair of reports disagree.
Next step
Most companies start with written rules for AI use.
The AI Use Policy is usually the first piece of work, and the first conversation is where we agree whether it is the right place for you to start.