Research notes
Before we suggest anything to a firm, we study its sector. Each note sets out what the public record shows, what waiting costs the business, the options weighed and the benchmark we would set. Every figure is checked against its source.
Banking
Lenders, NBFCs and banks: replacing core-adjacent systems, unsupported software, outages and the regulator’s view.
Fear of a failed system replacement
Research note 1
Lenders Do Not Fear Their Old Systems. They Fear One Weekend.
Research note 2
Before You Ask What a Replacement Costs, Ask What It Is Worth.
Research note 3
"Nothing Will Be Lost" Is a Promise. A Benchmark Is Something You Can Check.
Issue study · From the public record
When Replacing the System Is the Biggest Risk
Unsupported software and hardware
Research note 1
Unsupported Software Is Now a Board Matter. Most Firms Cannot Say Where It Is.
Research note 2
Your Software's Maker Has Set the Date. The Plan Can Still Be Yours.
Research note 3
"Accepted Again" Is Not a Plan. A Shrinking Register Is.
Issue study · From the public record
When the Maker Stops Fixing the Software
Outages at peak load
Research note 1
Every Outage Was Resolved. The Record Is What the Regulator Reads.
Research note 2
Your Busiest Days Are Your Growth Days. Old Systems Fail on Them.
Research note 3
Know Which Part Gives Way First, and Move It Before the Next Peak
Issue study · From the public record
When the Busiest Day Brings the System Down
Dependence on one vendor or shared provider
Research note 1
Only Your Vendor Understands the System. Here Is What the Public Record Shows.
Research note 2
Only One Firm Can Quote for Your System. A Second Quote Starts With a Document.
Research note 3
A Supplier Runs Your System. Here Is the Benchmark for Overseeing It.
Issue study · From the public record
When a Supplier Holds the System: Dependence in Financial Services
Weak patch and change process
Research note 1
The Regulator Now Looks at How You Change Your Systems. Most Old Systems Cannot Show a Change Was Safe.
Research note 2
Your Releases Happen at Midnight, by Hand. Four Ways Out, Weighed.
Research note 3
Your Security Fixes Are Waiting in a Queue. Here Is the Benchmark We Would Set.
Issue study · From the public record
The Change Nobody Could Test
Scarce skills for old systems
Research note 1
The Skills for Old Systems Are Running Out. The Knowledge Does Not Have To.
Research note 2
You Cannot Hire for Your Old System. You Can Stop Needing To.
Research note 3
The Scarce Skill Is Reading the Old Code. Here Is the Benchmark for Needing It Less.
Issue study · From the public record
When the Last Person Who Understands It Retires
Business rules buried in code
Research note 1
Your System Applies Its Rules Every Day. Nobody Can Say What They Are.
Research note 2
The Rules in Your System Were Decisions. The Business Can Make Them Again.
Research note 3
"We Documented It" Is Not the Same as Having the Rules. A Benchmark Shows the Difference.
Issue study · From the public record
When the System Is the Only Record of the Rules
Cannot connect to new services
Research note 1
Your Launch Has Been "Next Quarter" for Two Years. The Blocker Has Never Been Named.
Research note 2
Your System Is "Not AI Compatible". That Is Where the Decision Starts.
Research note 3
Your Staff Are the Connection Between Your Systems. Here Is the Benchmark for Ending It.
Issue study · From the public record
The Product That Could Not Launch
Regulator restrictions and penalties
Research note 1
The Regulator Can Now Stop a Lender's Growth Over Its IT. Most Boards Hear It Last.
Research note 2
The Regulator Named the Areas in Public. The Record Behind Them Can Be Ready First.
Research note 3
A Replacement Plan Needs Stages Someone Can Check. Here Is the Benchmark We Would Set.
Issue study · From the public record
Ten Months Without New Customers
Healthcare
Hospitals, payers and pharma: old clinical and billing systems, data rules and what the public record shows.
Unsupported operating systems and servers
Research note 1
Hospitals Keep Unsupported Servers for One Reason. It Is Rarely the Server.
Research note 2
New Digital-Health Work Is Waiting on Servers Nobody Can Change.
Research note 3
An Exception List That Only Grows Is Not a Plan. One That Shrinks Is.
Issue study · From the public record
When the Application Keeps the Old Machine
Missing basic security controls
Research note 1
Old Health Applications Lack the Basic Locks. The Reason Is Inside the Application.
Research note 2
The Old System Outside Your Controls Is the Question You Cannot Answer Yes To.
Research note 3
"Partially Implemented" Should Change Every Year. Here Is the Benchmark That Makes It.
Issue study · From the public record
When One Server Has No Second Lock
Cannot exchange records with other systems
Research note 1
Hospital Systems Rarely Pass Records to Each Other. The Connection Is Usually a Person.
Research note 2
Digital Health Now Asks for Records That Move. Many Hospital Systems Were Built to Keep Them.
Research note 3
Sharing One Record Should Not Mean Replacing Every System. Here Is the Benchmark We Would Set.
Issue study · From the public record
A Record System Built to Keep Records, Not to Share Them
Replacement is costly and risky
Research note 1
A Hospital Has No Quiet Weekend. What the Record Says About Replacing Old Systems.
Research note 2
Every Year the Replacement Waits, the New Work Waits With It.
Research note 3
Nobody Can Promise a Replacement Misses Nothing. A Benchmark Can Show It.
Issue study · From the public record
When Replacing the Old System Is the Riskiest Thing a Hospital Can Do
Dependence on an outside suppliers systems
Research note 1
When a Supplier's System Stops, a Hospital Learns What Depended on It. That Can Be Known Beforehand.
Research note 2
Your Hospital Can Choose Another Supplier. Its Own System Often Cannot.
Research note 3
How Much of Your Own System Do You Hold? Four Measures, Now and Where They Should Be.
Issue study · From the public record
When the Laboratory's Supplier Stops
Scarce skills for old in house systems
Research note 1
The Scarce Skill in an Old Hospital System Is Reading It. That Can Be Done Once.
Research note 2
The Changes Your Hospital Is Asked For Are Queuing Behind One Person.
Research note 3
How Many People Can Explain Your Hospital's System? Four Measures, Now and Where They Should Be.
Issue study · From the public record
When Only One Person Can Read the System
Data locked in old formats
Research note 1
Hospitals Keep Every Old Record. What Goes Missing Is What the Records Mean.
Research note 2
New Digital-Health Work Is Waiting on Records Only an Old System Can Read.
Research note 3
Data a New Tool Cannot Read Is Not Ready. Here Is the Benchmark for Ready.
Issue study · From the public record
When the Old System Is the Only Way Into the Archive
Harm to patients when systems go down
Research note 1
When Hospital Systems Stop, Care Stops. Which Ones It Rests On Can Be Known Beforehand.
Research note 2
The Application Your Wards Rely On Most Is Often the Oldest. Four Ways to Answer That, Weighed.
Research note 3
How Much of What Care Rests On Have You Mapped? Four Measures, Now and Where They Should Be.
Issue study · From the public record
When the Systems Care Depends On Stop
Retail
Retailers and marketplaces: peak-day outages, old order and stock systems, and the cost of standing still.
Unsupported shop software
Research note 1
Online Shops Stay on Unsupported Versions for One Reason. It Is Rarely the Platform.
Research note 2
New Offers Are Waiting on Shop Code Nobody Can Change.
Research note 3
An "Unsupported" Entry With No Date Is Not a Plan. A Shrinking List of Custom Code Is.
Issue study · From the public record
Hundreds of Shops in One Day
Old php and databases under the shop
Research note 1
About Half of PHP Websites Run a Version the PHP Project No Longer Fixes. The Reason Is Rarely Neglect.
Research note 2
A Few Old Parts Hold the Whole Shop on an Old Version. Everything Else Waits With Them.
Research note 3
An Upgrade Nobody Can Check Is a Gamble. A Shrinking List of Blocking Parts Is a Plan.
Issue study · From the public record
Upgrade It and See
Systems that do not connect
Research note 1
Retail Systems Rarely Share What They Know. The Connection Is Usually a Person.
Research note 2
Invoices Now Have a Clock. Systems Joined by a Monthly File Run Behind It.
Research note 3
Every Crossing Between Your Systems Should Have an Owner. Here Is the Benchmark We Would Set.
Issue study · From the public record
A Portal Nobody Could Build On
Wrong or unreliable data
Research note 1
Retail Figures Are Not Wrong by Accident. Each One Is Made Wrong Somewhere.
Research note 2
A Price History and a Ninety-Day Answer: What Waits on Retail Data Nobody Trusts.
Research note 3
Before Old Data Moves, Someone Should Write Down Where It Cannot Be Trusted.
Issue study · From the public record
Figures Nobody Can Trust
Accounts and systems held by someone else
Research note 1
Many Firms Cannot Say Whose Name Is on Their Own Systems. They Find Out on the Worst Day.
Research note 2
A Firm That Does Not Hold Its Own Systems Cannot Plan a Move.
Research note 3
Leaving Someone Else's Systems Is Not a Weekend. It Is a List, Then One Module at a Time.
Issue study · From the public record
Whose Name Is on the Account
Replacement is costly and disruptive
Research note 1
Every Retail Replacement Story You Have Heard Is One Kind of Project. Yours Probably Is Not.
Research note 2
The Cost of Waiting Belongs Beside the Fear of Replacing. Four Ways Forward, Weighed.
Research note 3
A Replacement You Can Pause Is One You Can Start. The Measures to Hold It To.
Issue study · From the public record
Replaced All at Once
Slow at peak times
Research note 1
Every Shop Has a Part That Gives Way First. Most Find Out Which on the Day.
Research note 2
Sale Days Your Shop Cannot Hold. More Servers Are One Answer of Four.
Research note 3
Nobody Can Promise You a Peak Day. You Can Know Where It Will Be Decided.
Issue study · From the public record
Twenty-Five Thousand a Minute
Manufacturing
Manufacturers: ERP replacements, plant systems nobody can change, and supplier and tax deadlines.
Replacement goes wrong at go live
Research note 1
Manufacturers Keep Their Old Applications for One Reason. It Is the Go-Live Day.
Research note 2
A New System Can Pass Every Test and Still Miss the Old One's Rules.
Research note 3
"Who Said It Was Ready?" Is a Question to Answer Before Go-Live, Module by Module.
Issue study · From the public record
When a Go-Live Costs a Quarter's Sales
Unsupported erp operating systems and databases
Research note 1
Old Servers Outlive Their End Dates for One Reason. Nobody Has Listed What Stands on Them.
Research note 2
One Old Application Can Keep a Whole Server Past Its End Date. It Can Be Rebuilt by Itself.
Research note 3
An ERP Move Cannot Be Priced While Your Own Programs Beside It Are Unwritten.
Issue study · From the public record
Past the End Date
Cannot connect machines and systems
Research note 1
The Plant Says One Number and the ERP Says Another. The Public Record Says That Is Where AI Pilots Stop.
Research note 2
Your Planner Types the Same Figure Three Times. Four Ways to Stop It, Weighed.
Research note 3
Off the Clipboard Starts With Counting the Copies.
Issue study · From the public record
Where the Figures Cross by Hand
Knowledge held by outside partners or one person
Research note 1
Ask Who Knows How the Dispatch System Works, and the Answer Is a Phone Number.
Research note 2
Only One Firm Can Quote for Changes to Your System. A Record You Hold Changes That.
Research note 3
When the One Person Who Knows Is on Leave, the Firm Should Still Have an Answer.
Issue study · From the public record
A Record the Firm Holds
Scarce vb6 and rpg skills
Research note 1
The Advert for a VB6 Developer Goes Unanswered. The Public Record Says It Is Not the Advert.
Research note 2
Every Change Waits on One Scarce Skill. Four Ways Out, Weighed.
Research note 3
A Technology You Can Hire For: The Benchmark for Moving an Old Application, Module by Module.
Issue study · From the public record
Not on the List
Rules and reports buried in erp customisations
Research note 1
Ask How a Product Cost Is Worked Out, and the Answer Is "Whatever the System Says". The Rules Are in Programs Nobody Has Read.
Research note 2
A Price Agreed Years Ago Can Still Be Running. You Cannot Change a Rule You Have Never Read.
Research note 3
A Change to a Pricing Rule Should Not Be a Leap of Faith. Here Is the Benchmark We Would Set.
Issue study · From the public record
Heavily Customised
Unreliable stock and production data
Research note 1
A Wrong Stock Figure Is Made Somewhere. Most Manufacturers Never Find Out Where.
Research note 2
A Stock Count Corrects the Records. The Work That Waits Needs the Cause Fixed.
Research note 3
Before Old Figures Are Carried Into a New System, Know Where They Were Made.
Issue study · From the public record
Data Issues
Logistics, travel and hospitality
Carriers, airlines and hotels: scheduling and booking systems, outages and joining old systems to new partners.
Systems fail under load
Research note 1
Every Booking System Has a Ceiling. Most Firms Learn Theirs in the Busiest Week.
Research note 2
The Weeks That Earn the Year. More Servers Are One Answer of Four.
Research note 3
The Day the Plan Changes Is the Day That Counts. Here Is the Benchmark We Would Set.
Issue study · From the public record
Could Not Keep Up With the Changes
Old servers and operating systems
Research note 1
The End Dates Are Published. The List of What Runs on Each Old Server Is Not.
Research note 2
One Old Program Can Keep a Server Switched On. Extended Support Is One Answer of Four.
Research note 3
The Plan to Leave the Old Servers Has One Line for the Hard Part. Here Is the Benchmark We Would Set.
Issue study · From the public record
Still in Service
Inherited systems nobody understands
Research note 1
You Bought the Business, and Its Systems Came With It. Here Is What the Public Record Shows.
Research note 2
Nobody Left to Ask. Four Ways to Deal With an Inherited System, Weighed.
Research note 3
A Year After the Deal You Still Run Two of Everything. Here Is the Benchmark We Would Set.
Issue study · From the public record
Inherited, and Still in Service
Too slow and costly to replace
Research note 1
The Old System Still Works. That Is Why the Replacement Never Starts.
Research note 2
Everything Waits for "After the Replacement". Four Ways Forward, Weighed.
Research note 3
Finished Should Mean Matched. The Benchmark We Would Set for a Replacement.
Issue study · From the public record
Too Big to Approve
Too many separate systems
Research note 1
Your Systems Each Work. The Trouble Is Where a Consignment Crosses Between Them.
Research note 2
Consignments Now Meet Tax Clocks. Replacing Everything Is One Answer of Four.
Research note 3
Your Systems Are Already Joined, by Files, Scripts and Spreadsheets. Here Is the Benchmark We Would Set.
Issue study · From the public record
Systems That Do Not Share What They Know
Scarce skills and missing documentation
Research note 1
The Rules for Your Fares Live in Code Two People Can Read. Here Is What the Public Record Shows.
Research note 2
Two People Know How Your System Works. Four Ways to Stop Depending on Them, Weighed.
Research note 3
A Record Your Staff Open Before They Pick Up the Phone. Here Is the Benchmark We Would Set.
Issue study · From the public record
Ask the Person Who Wrote It
Software and SaaS vendors
Software companies: inherited code, release paths, security obligations and products customers still run.
Product built on an unsupported technology
Research note 1
Software Firms Know Their Product Stands on Unsupported Technology. What They Lack Is a List.
Research note 2
There Is No Newer Version to Move To. A Software Firm Does Not Have to Stop Selling to Leave.
Research note 3
"It Seems Fine" Is Not a Test. An Upgrade Your Own Engineers Can Check.
Issue study · From the public record
Strongly Recommends That You Replace
Few developers for the old technology
Research note 1
Software Firms Say They Cannot Hire for Their Old Technology. What Holds Them Back Is How Few People Can Read the Code.
Research note 2
The Advert Has Been Open for Months. A Software Firm Can Stop Waiting for the Old Skill.
Research note 3
A Newcomer's First Change Should Not Need a Senior Engineer's Memory. The Benchmark We Would Set.
Issue study · From the public record
Hiring for the Oldest Code
Everything depends on one person
Research note 1
One Person Knows How the Product Works. What the Firm Lacks Is a Record That Person Has Checked.
Research note 2
A Software Firm That Rests on One Person Cannot Say Who Holds What. Four Ways Forward, Weighed.
Research note 3
Only One Person Can Put the Product Live. The Benchmark for a Release Anyone Can Make.
Issue study · From the public record
Who Holds What
Weak testing and release checks
Research note 1
Software Releases Are Checked Against the Faults Already Known. Customers Find the Rest.
Research note 2
Releasing Often Without Fear Is the Opportunity. Four Ways to Get There, Weighed.
Research note 3
A Way Back Nobody Has Tried Is Not a Way Back. The Benchmark for a Release You Can Check.
Issue study · From the public record
When a Release Goes Out Thinly Checked
Old data left in a forgotten store
Research note 1
Your Product Still Has a Data Store From Its First Version, and It Is on Nobody's List. What the Firm Lacks Is a List Taken From the Code.
Research note 2
Your Policy Says the Record Is Deleted, and Nobody Has Read What the Code Does. Four Ways to Find Out, Weighed.
Research note 3
The Product Moved to New Storage Three Years Ago, and the Old Store Is Still Running. A Benchmark for Every Old Store.
Issue study · From the public record
The Store the Product Stopped Using
Desktop only or dated user interface
Research note 1
"Is There a Web Version?" Has Been "On the Roadmap" for Years. What the Firm Lacks Is a List of Its Screens.
Research note 2
You Were Told a Web Version Means Rebuilding the Whole Product First. It Can Reach the Web One Module at a Time.
Research note 3
The New Screens Look Better, and Your Oldest Customer Says the Totals Are Wrong. A Benchmark for Every Rebuilt Screen.
Issue study · From the public record
From the Desktop to the Browser
Rewrite is risky
Research note 1
Rewrites Lose What Nobody Listed. The Old Product Is the List.
Research note 2
Halfway Through a Rewrite, the Money Is Spent and Nothing Ships. Let the Old Product Be the Judge.
Research note 3
Eighteen Months In, With Nothing to Ship. The Benchmark We Would Set Before a Rewrite Starts.
Issue study · From the public record
The Rewrite That Shipped Without the Old Features
Ai tools used without review
Research note 1
AI Tools Wrote the Code Quickly. Nobody Was Given the Time to Read It.
Research note 2
Almost Right, but Not Quite. Four Ways to Handle Code Your AI Tools Wrote, Weighed.
Research note 3
One Way In. A Benchmark for How Changes Reach Your Live Product.
Issue study · From the public record
Built Fast, Never Read
Government and public sector
Councils, departments and agencies: case and benefits systems, failed replacements and accessibility rules.
Unsupported hardware and software
Research note 1
Nobody Can Say How Much of Your Department Runs on Unsupported Systems. Here Is What the Public Record Shows.
Research note 2
Your Oldest Server Stays Because One Application Cannot Leave It. Four Ways Out, Weighed.
Research note 3
The Fix for Your Old Systems Is Too Big to Fund as One Project. Here Is the Benchmark We Would Set.
Issue study · From the public record
Four of the Eleven
Scarce skills for cobol and assembly
Research note 1
The People Who Understand Your Oldest System Are Retiring. Here Is What the Public Record Shows.
Research note 2
A Public Service Should Not Rest on a Retirement Date. Four Ways Forward, Weighed.
Research note 3
Every Question About Your Old System Waits for One Person. Here Is the Benchmark We Would Set.
Issue study · From the public record
A Dwindling Number of People
Locked to one supplier
Research note 1
Your Supplier's Contract Has an End Date You Cannot Use. Here Is What the Public Record Shows.
Research note 2
Your Contract's End Date Means Little Until You Can Describe Your Own System. Four Ways Forward, Weighed.
Research note 3
Leaving Your Supplier Does Not Have to Be One Handover Day. Here Is the Benchmark We Would Set.
Issue study · From the public record
Only the Supplier Can Describe It
Replacement fails or overruns
Research note 1
Public Replacements Overrun, Fail at Go-Live or Go Unused. Here Is What the Public Record Shows.
Research note 2
A Deferred Replacement Is Still a Decision. Four Ways to Replace an Old System, Weighed.
Research note 3
"Live" Is Not "In Use". Here Is the Benchmark We Would Set for a Replacement.
Issue study · From the public record
One Go-Live Day, and What It Stakes
Upkeep absorbs the budget
Research note 1
The Largest Line in Your Technology Budget Is the One Nobody Can Explain. Here Is What the Public Record Shows.
Research note 2
Every New Service Waits Because the Budget Is Already Spent on the Old Ones. Four Ways to Make Room, Weighed.
Research note 3
Your Team Spends Its Year Keeping the Old System Alive. Here Is the Benchmark We Would Set.
Issue study · From the public record
Eighty Per Cent on Standing Still
Wrong outputs trusted as correct
Research note 1
When a Figure Is Questioned, "the System Shows It" Is Often the Only Answer. Here Is What the Public Record Shows.
Research note 2
Nobody Has Set Your System Beside the Rules It Was Built to Apply. Three Ways to Check, Weighed.
Research note 3
Every Figure Your System Produces Should Trace to a Written Rule. Here Is the Benchmark We Would Set.
Issue study · From the public record
As Per System
Thin or missing documentation
Research note 1
Your System's Manual Describes a System That No Longer Exists. Here Is What the Public Record Shows.
Research note 2
A New Officer Takes Charge of Your System With Nothing to Read. Three Ways to Change That, Weighed.
Research note 3
Every Document About Your System Goes Out of Date. Here Is the Benchmark We Would Set.
Issue study · From the public record
Incomplete and Uneven
Telecom
Operators: billing and network-support systems, quality-of-service rules and security obligations.
Customer data wrong or incomplete
Research note 1
Operators Clean Their Customer Records Every Year. What Nobody Has Found Is Where the Records Go Wrong.
Research note 2
Cleaned, and Wrong Again. Four Ways to Make Customer Records Stay Right, Weighed.
Research note 3
Ready to Move Is Not the Same as Known. Where Your Customer Records Are Now, and Where They Should Be.
Issue study · From the public record
Identify and Record
Known security fixes never applied
Research note 1
Known Flaws Stay Open for Years. What Nobody Writes Down Is What the Fix Would Break.
Research note 2
Applied, and Checked by Your Own Team. Four Ways to Deal With Security Fixes That Keep Waiting, Weighed.
Research note 3
Fixable Is Not the Same as Fixed. Where Your Applications Stand on Security Fixes Now, and Where They Should Be.
Issue study · From the public record
Known Fixes, Still Waiting
Locked to legacy vendors
Research note 1
Most Operators Say They Depend on Their Legacy Vendors. What Few Hold Is Their Own Record of What They Run.
Research note 2
One Price at Renewal, and Nothing to Compare. Four Ways to Deal With a Vendor You Depend On, Weighed.
Research note 3
Tied a Little Tighter Every Year. Where Your Dependence on a Vendor Is Now, and Where It Should Be.
Issue study · From the public record
Only the Vendor Can Explain It
End of life hardware
Research note 1
Operators Know Which Servers Are Old. What Nobody Has Written Down Is What Runs on Them.
Research note 2
Spares Buy Time, Not a Way Off. Four Ways to Deal With Servers Past Their Support, Weighed.
Research note 3
New Servers Are Not the Same as Off the Old Ones. Where Your Old Machines Are Now, and Where They Should Be.
Issue study · From the public record
What Each Old Server Carries
Too risky to move off old systems
Research note 1
Every Operator Agrees the Old Billing Applications Must Go. What We Found Is Why Nobody Names the Date.
Research note 2
Every Billing Change Waits on a System Nobody Dares Touch. Four Ways Off the Old Applications, Weighed.
Research note 3
You Are Asked to Approve a Move Nobody Can Price. Where Your Replacement Plan Is Now, and Where It Should Be.
Issue study · From the public record
A Move to a New Billing System
Safety of life services depend on the old network
Research note 1
Operators Can Count the Accounts They Marked. What Nobody Can Count Is Who Was Never Asked.
Research note 2
Recorded in One System Is Not Known in the Next. Four Ways to Deal With a Status That Gets Lost, Weighed.
Research note 3
A New Application Is Not the Same as Every Rule Carried Across. Where Your Records Are Now, and Where They Should Be.
Issue study · From the public record
Who Depends on the Line: What an Operator's Records Could Say
Education
Universities and schools: student records, examinations, separate systems and the regulator’s deadlines.
Replacement is very costly
Research note 1
Your Replacement Was Scoped From the Systems Everyone Could Remember. Here Is What the Public Record Shows.
Research note 2
While One Large Figure Waits for Approval, New Options Wait Too. Four Ways to Replace, Weighed.
Research note 3
Your Replacement Is One Programme With One Go-Live, Years Away. Here Is the Benchmark We Would Set.
Issue study · From the public record
Priced Before It Was Read
Unsupported databases
Research note 1
Nobody Can Say What a Database Upgrade Would Break. Here Is What the Public Record Shows.
Research note 2
One Old Application Can Keep Every Other on an Unsupported Database. Four Ways Out, Weighed.
Research note 3
The Upgrade Is Your Team's to Do. Here Is the Benchmark We Would Set to Check It Against.
Issue study · From the public record
Out of Extended Support
Locked to one supplier
Research note 1
When the Supplier's Contract Comes Up, Nobody Can Write the Tender. Here Is What the Public Record Shows.
Research note 2
Only the Supplier Can Say What Your System Does. Four Ways Forward at the End Date, Weighed.
Research note 3
Changing Supplier Does Not Have to Rest on One Handover Day. Here Is the Benchmark We Would Set.
Issue study · From the public record
A Contract That Outlasts Its Term
Slow or faulty results processing
Research note 1
Your Results Rest on Rules Written Down Only Inside the Application. Here Is What the Public Record Shows.
Research note 2
The Rules Your Results Application Applies Keep Changing. Four Ways to Make a Change You Can Check, Weighed.
Research note 3
One Step in Results Processing Takes Most of the Time. Here Is the Benchmark We Would Set.
Issue study · From the public record
The Rules Inside a Results Application
Too many separate systems
Research note 1
The Fees Office Says Paid and the Examination Section Says Due. Here Is What the Public Record Shows About Separate Systems.
Research note 2
When a Record Is Typed in Three Offices, Replacing Everything Is One Answer of Four.
Research note 3
Your Systems Are Already Joined, by Scripts, Files and Spreadsheets. Here Is the Benchmark We Would Set.
Issue study · From the public record
Separate Systems That Do Not Agree
Want this research applied to your system?
Start with a free Reliability Review, or see what the Legacy System Specification Assessment produces.