Correcting an approved record needs a deliberate path
Keep a mistaken entry repairable without silently rewriting an earlier decision.
Read / Discuss / Try an example
Small decisions behind a useful service
Worked questions to help a team explain what it needs before choosing the build. Articles are in English for projects connected to Estonia.
Business applications
Customer journeys
An error message should tell the person what can happen next
Translate a failed operation into a useful business explanation without exposing private diagnostics.
Language and review
Make language availability a clear promise the business can keep
Tell visitors which information and follow-up are available rather than relying on a flag alone.
Access and responsibility
A successful login is different from permission to approve
Connect access to the actual business decision a person is authorised to make.
Business applications
Agree which work belongs in a report total
A dashboard number should have a definition that staff can reproduce from example records.
Maintenance and continuity
Leave the next service owner with decisions, not just passwords
A usable handover explains what the tool supports and who can change it.
Business applications
A deadline field should explain what happens on that date
Agree the business event before choosing a date format or reminder.
Websites and content
“No records” can mean several different things
Explain whether the work is finished, filtered, unavailable or not yet started.
Maintenance and continuity
A data export is only one part of leaving a business application
Check whether the organisation can understand and use its information after a supplier relationship ends.
Accessibility and usability
Try the important service without a mouse before judging the redesign
A focused keyboard walkthrough can reveal barriers that a screenshot cannot show.
Access and responsibility
A notification should reach a responsible role, not an abandoned inbox
Plan who receives the message and what information belongs in it.
Content and responsibility
A public case note should not inherit an internal comment
Separate material approved for publication from the working information behind it.
Customer journeys
Does the first enquiry really need an attachment?
Separate the information needed to begin a conversation from the material needed to perform the work.
Access and responsibility
What should a customer see after a project workspace closes?
A project ending changes the useful tasks, but does not automatically answer every access and document question.
Connected work
A connection needs an exception queue people can understand
Show unresolved transfers as work with an owner, rather than hiding them behind a successful-looking dashboard.
Access and responsibility
Who approves a change in access when responsibilities move?
A staff change should trigger an understandable decision about permissions, rather than a copied account.
Websites and content
Describe what a service plan includes before designing the comparison
A plan comparison should help a customer choose, without suggesting unsupported availability or an invented price.
Language and review
Agree a small Estonian–English service glossary before publishing
Important service terms can change how customers understand an offer.
Customer journeys
“Uploaded” and “ready to use” should mean different things
A document journey needs feedback that reflects what the business has actually completed.
Connected work
Two records with the same company name are not always duplicates
Define what identifies the business record before merging information during a migration.
Connected work
Keep a customer reference as a reference, not an accidental number
A code can lose meaning when a spreadsheet or connection treats its characters as a quantity.
Orders and information
A discontinued product page can still answer a useful question
Help existing customers find the right next step without presenting an unavailable item as orderable.
Access and responsibility
A useful discovery sample should reveal the task without exposing the customer
Prepare demonstration records that preserve the difficult decision while removing unnecessary real information.
Business applications
What happens when two colleagues edit the same record?
Choose how a business tool protects a later change from silently replacing another person’s work.