How to record the process video we need

Three minutes of screen are worth more than ten emails, and you need nothing special

A smartphone filming a computer screen while someone works

Why a video says more than a written description

A process told in words always comes out tidier than it really is, because whoever describes it skips the steps they now do without thinking, and those are exactly the steps you need in order to understand the work

In a screen recording you see all of it instead, the window that opens slowly, the field that has to be filled in before the other one or the program complains, the sheet open on the side you copy a code from, the step nobody would ever have mentioned in an email because it seems obvious

That's why the first thing Muffin Suite asks for is a short screen recording while you do the work, not a document, not a diagram, the real work as it comes out of your hands

Before you press record, get the real data out of the way

Real customer data, passwords typed on screen, confidential attachments and screens with sensitive material on them must never end up in the recording, use a made-up case or a test document, and if you haven't got one cover the fields that must not get out

The simplest way is to work on a test customer or on an old job that is already closed, with the names changed, since whoever watches doesn't care who the customer is, they care which fields you touch and in what order

If your program won't let you run a made-up case, it's fine to record the real one and then cover the parts to hide with a rectangle before sending it, or stop the recording the moment you type the password and start again afterwards, the login isn't the interesting part

Do the work the way you do it on a Tuesday morning

The temptation is to put together a nice demonstration, with the files ready and the perfect case, and it's the least useful thing you can do, because the perfect case is the one that gives nobody any trouble

Do it the way you always do, at your own speed, with the shortcuts you use, with the windows arranged the way you usually keep them, without explaining as if you were teaching a class

If something gets in the way while you're recording, the code that doesn't exist, the invoice written in a strange way, the field that won't accept the value, don't cut it out, that's the most valuable moment in the whole recording, because that's where you see what the system will have to do when things don't add up

Talk while you do it

Your voice is worth as much as the screen, because it explains the why behind what you see

You don't need a prepared commentary, it's enough to say out loud what goes through your head while you work, I take this from here, I always check this one because it went wrong once, I leave this field empty if the customer is Italian

Sentences like those are the rules of your process, said in the only way they really exist, and they are what it takes to write an automation that behaves the way you expect instead of the way it likes

What you record with, without installing anything

On Windows screen recording is already there, you find it in the system capture tools, the ones you use to take a screenshot also have a video mode, and for an office process they are enough

If you're happier with your phone, film the computer screen and hold it steady, the quality is good enough as long as the fields can be read

No editing needed, no title needed, the recording doesn't have to be a pretty thing, if you stumble carry on, and if you get it all wrong start again from the top, it takes you less time than cutting

How long it should last

The right recording lasts as long as the work on a single case, from start to finish, without skipping the boring part in the middle

If one job takes you three or four minutes, that is already a complete and useful recording

If the process is long, break it into two or three pieces instead of making a single half-hour file, and if you have a normal case and one that goes wrong, record both, that's the bit of recording that pays for itself best

What happens after you've sent it

The recording gets watched, and from there you can tell which steps are mechanical and always the same, which ones need a person to look and decide, and whether the program you use can be driven through its screens, which holds for programs with no direct integration at all as well

Then a few questions come back, because a recording clears up most of the doubts, not all of them

If you want to turn up already knowing what that work weighs, the Work out the savings page adds up the hours using your numbers, and the recording explains the rest

Where to send it

You can send the recording on WhatsApp to 352 012 5997 or by email to info@muffin-suite.com, and if the file is too heavy for email upload it to a shared link and send us that

If you'd rather not record anything, that's fine too, we can have a call and you show me live by sharing your screen, from the Contact page we set a time that suits you

What people usually ask us

No, real customer data, passwords or confidential documents must never end up in the process recording, better to use a test case or an old job with the names changed, and if something stays on screen you cover it before sending it
No, on Windows screen recording is already in the system capture tools, and filming the monitor with your phone works too, the quality is good enough as long as the fields can be read, there is nothing to install
Both, and if you can only pick one pick the one that goes wrong, because the case that runs smoothly teaches nothing, while the code that doesn't exist or the badly written document show what the system will have to do when the data doesn't add up
As long as the work on a single case takes, from start to finish without skipping the boring part, and if the process is long it's worth breaking it into two or three pieces instead of sending one very long file
Yes, and it counts as much as the screen, because the sentences you say while working, I always check this one, I leave this field empty in that case, are the rules of the process, and they are what it takes to write an automation that behaves the way you expect
That's fine too, we can have a call and you show the process live by sharing your screen, the recording is only there because it's more convenient for you, it isn't a requirement for talking to Muffin Suite

Show us what you still do by hand

Describe the process or send a short screen recording and we'll tell you what can be automated

WA