Good Systems Have Good Manners
An appointment reminder arrives with the time, the meeting link, and a short note about what to bring. You open it, find what you need, and go on with your day. The person who sent it has spared you a search through your inbox. I consider that excellent manners.
We tend to talk about systems in the language of efficiency. Some steps can be streamlined and tasks automated. I’m interested in those things, too. I also want to know how it feels to be the person moving through the process.
Does the form ask a sensible question? Does the email explain what happens next? Can someone tell whether you received what they sent? Those details are part of doing business with consideration.
Take an intake form. It might be beautifully designed and still ask someone to supply the same information they already emailed you. It might require a detailed answer to a question they aren’t ready to answer yet. Somewhere in the middle, a potential client may wonder whether an exploratory conversation requires this much homework.
A considerate process asks for the information needed at that stage. It explains an unfamiliar question and leaves room for an honest “I’m not sure yet.” Where possible, it carries forward information the person has already provided. There’s a little less work for the person on the other side.
Good manners also include acknowledging receipt. Imagine handing someone a folder and having them turn away without a word. Online, that same silence can happen after a payment, an application, or a carefully completed questionnaire. A simple confirmation helps close the exchange: “Thank you. I have what I need, and I’ll be in touch by Thursday.”
Of course, Thursday now needs a place on someone’s calendar or in their task list. A courteous message creates a commitment, and the system behind it should help you keep it. Otherwise, the beautiful confirmation becomes the opening act for an awkward follow-up.
This is why I like looking at communication and operations together. The email makes a promise. The workflow gives that promise an owner and a date. Both deserve attention.
Consideration matters inside the business, too. A colleague should be able to find the current version of a document without digging through an archaeological site. A recurring task should come with enough context to do it well. A deadline should mean something more specific than “soon,” which can mean Tuesday to one person and next month to another.
You can bring a little courtesy into an existing process without replacing every tool you own. Choose one interaction that regularly produces questions. Perhaps clients ask where to upload a file. Perhaps a team member always needs to confirm which template to use. That repeated question is a useful place to look.
Walk through the experience as the other person. Read the instructions without filling in the missing pieces from your own knowledge. Place the necessary link next to the action it belongs to. Name the person responsible for the next step. Check that reminders stop once the work is complete.
An automated message can do this beautifully when it arrives at the right moment with useful information. It can also become irritating when it keeps asking someone to do something they finished yesterday. The technology needs enough care around it to stay helpful.
I want business systems to make the day a little easier for everyone involved. That includes the owner who answers the same question every week, and the client who was never quite sure where to find the answer.
Good manners help people move comfortably through an interaction. Your systems can offer that same consideration, one clear instruction and one kept promise at a time.