Thinking

Notes on business processes, automation, and digital systems.

Thinking / Automation

What Automation Actually Changes

August 1, 20262 min read

Many people think automation is about doing the same work faster. In reality, the biggest change is much simpler: the process no longer depends on someone remembering every step.

In manual workflows, small tasks pile up quickly. Information is copied between systems, spreadsheets are updated by hand, messages are sent manually, and someone has to remember what comes next. Each individual task seems insignificant, but together they consume time, create inconsistencies, and make the business harder to manage.

Automation changes the process itself. Repetitive actions happen automatically, information moves where it needs to go, and the next step is triggered without constant follow-up. Instead of spending time on routine work, people can focus on decisions that actually require human judgment.

Thinking / Process

Small businesses can't afford not to automate

July 30, 20262 min read

Automation is often postponed until a business becomes "big enough." But the logic works the other way around.

A large company can compensate for inefficient processes with more people. A small business doesn't have that capacity.

I saw this in a company working with cars. Everyone was constantly busy, yet no one knew exactly who was responsible for each task or where to find the information they needed. Agreements remained buried in chats, next steps existed in someone's memory, and responsibility kept shifting between employees.

Thinking / Case note

From a Client Message to the Right Technician

July 28, 20263 min read

For one company working with CNC equipment, every new client request started a chain of manual actions.

A manager had to copy the message into ChatGPT, shorten and structure it, search through the technician database, contact suitable candidates and track their responses.

None of these actions was particularly difficult. The problem was that every request depended on someone completing every step correctly - without losing information or forgetting to update the result.

Thinking / Case note

Case Study: Removing Translation from the Workflow

July 25, 20262 min read

A minute spent translating a message does not seem like much - until it happens hundreds of times a day.

While visiting a car sales and repair company, I noticed that every conversation with a foreign-language customer followed the same routine. The sales manager copied messages from WhatsApp into ChatGPT, translated them, wrote a reply, translated it back, and finally sent it to the customer. The process worked, but it interrupted every conversation and added unnecessary manual work.

Instead of trying to make translation faster, we removed it from the workflow altogether.

Thinking / Observation

7 Digital Habits That Are Becoming Standard for Modern Companies

July 23, 20264 min read

Not long ago, tools such as CRM systems, workflow automation and real-time dashboards were seen as signs of advanced digital transformation. Today, they are gradually becoming part of the basic infrastructure required to run a clear and manageable business.

The difference is not simply that modern companies use more software. It is that information, actions and responsibilities are connected into a consistent process.

Customer data, enquiries, tasks and interaction history are usually stored in one central system rather than scattered across spreadsheets, chats and personal notes. This gives the team a single source of current information and reduces dependency on individual employees.

Category	Examples
Enquiry and contact data	Your name; email address, telephone number or another contact method you choose; and your comment or brief project description.
Correspondence and project data	Messages, attachments, meeting notes, requirements, proposals, decisions and other information you provide during discussions or a working relationship.
Business contact data	A person’s name, role, company, work contact details and the public source from which those details were obtained.
Email and engagement data	Subscription status, consent record, delivery and bounce events, unsubscribe or suppression status, and—where enabled—email opens and link clicks.
Technical data	IP address, date and time, requested page, browser or device information, referrer and security/error log information generated by the server.

Purpose	Typical legal basis
Respond to an enquiry, assess a proposed project, arrange discussions and prepare a proposal.	Steps taken at your request before entering into a contract; legitimate interests in responding to business enquiries.
Enter into, administer and deliver a project or service.	Performance of a contract; compliance with legal obligations; legitimate interests in managing the working relationship.
Maintain correspondence, records, security, service reliability and evidence of agreed terms.	Legitimate interests in operating and protecting the business and establishing, exercising or defending legal claims; legal obligations where applicable.
Send a newsletter or other optional marketing requested through the website.	Your consent. You may withdraw it at any time.
Send limited, relevant B2B outreach to publicly listed professional contacts.	Legitimate interests in promoting services to organisations that may reasonably find them relevant, where permitted by the law applicable to the recipient. Consent is used where the applicable law requires it.
Measure delivery and engagement with emails, including opens and link clicks where enabled.	Consent for voluntary subscribers where required; otherwise legitimate interests only where the applicable law permits and the impact on recipients is proportionate.

Data	Typical retention
Enquiries and ordinary business correspondence	Up to two years after the last meaningful communication, unless a longer period is reasonably necessary for a contract, legal obligation or legal claim.
Client and project records	For the duration of the working relationship and afterwards for the period required by applicable contractual, tax, accounting and limitation rules.
Newsletter and marketing records	Until you unsubscribe, withdraw consent or the purpose ends. Consent and unsubscribe records may be retained as necessary to demonstrate compliance.
Suppression records	The minimum identifier needed to honour an opt-out may be kept for as long as reasonably necessary to prevent further marketing.
Email engagement events	Normally up to two years after the relevant interaction or last engagement, unless aggregated or anonymised earlier.
Server and security logs	For a limited period proportionate to security, troubleshooting and operational needs, unless an incident requires longer retention.