BLOG

Business systems and preparation before commissioning

Practical perspectives for people who are considering business system development.

A workspace for organizing operational problems, workflows, and priorities

Articles are ordered from before commissioning to development and post-release operations.

Continuous improvement8 min

A guide for commissioning business systems

Why business systems should not be treated as finished after launch

What tends to happen when a system stops at the initial release, and why the same team can be valuable for operations and improvement.

  • What cannot be decided before the initial release
  • Problems that remain when the initial project simply ends
  • The value of keeping the initial team involved
Before commissioning7 min

A guide for commissioning business systems

What clients should understand before ordering a business system

How to organize purpose, scope, priorities, acceptance criteria, and operations before asking a development company for a proposal.

  • Why system development cannot be completely outsourced
  • The purpose to define before requirements
  • Why current work should not be digitized unchanged
Before requirements6 min

A guide for commissioning business systems

What to decide before writing requirements

The purpose, success conditions, users, and boundaries to clarify before turning a business problem into a requirements document.

  • Why purpose comes before feature lists
  • How to define the scope of the first release
  • How to set priorities before discussion expands
Workflow review6 min

A guide for commissioning business systems

Why you should not digitize the current workflow as-is

How to review duplicated input, exceptions, and hidden rules before turning a paper, spreadsheet, or chat-based process into a system.

  • Why the current process is not the same as the requirement
  • How exceptions increase system cost
  • Where duplicated input can be reduced
Preparing for a consultation6 min

A guide for commissioning business systems

What to prepare before consulting about a business system

A practical checklist of current materials, pain points, unknowns, and decisions that make an initial system consultation more useful.

  • Which current materials to bring
  • How to describe the real pain points
  • Why unresolved questions should be shared
Priorities6 min

A guide for commissioning business systems

How to prioritize features in a business system

A way to separate essential features from useful additions by looking at workflow impact, frequency, risk, and the scope of the first release.

  • How to separate must-have and nice-to-have features
  • How to judge frequency and impact
  • Why the first release should be narrow
Acceptance testing7 min

A guide for commissioning business systems

What to check in an acceptance test for a business system

A practical acceptance-test view organized around real workflows, permissions, data, and exception handling from the client's perspective.

  • The purpose of acceptance testing
  • How to test the real workflow
  • How to check permissions and data
Operations and improvement6 min

A guide for commissioning business systems

What clients should do after a business system goes live

How to organize post-launch operations, questions, improvement requests, and the support structure instead of treating launch as the end.

  • What happens after launch
  • How to set a support contact
  • How to organize improvement requests
Spreadsheet management6 min

A guide for commissioning business systems

Signs that spreadsheet management is reaching its limit

How to decide whether Excel or spreadsheets are still appropriate, and when to consider systemization for shared business work.

  • Signs that spreadsheet management is reaching a limit
  • Duplicate entry and stale updates
  • Dependence on one person and unclear permissions