This kind of process is extremely valuable and should be done by devs more often. Start from the start and follow whatever your application tells you to do. Note down when it doesn't tell you where to go or what to do. You'd be surprised by just how many things you do automatically while working because you know the little tricks and things to get by, and that wording doesn't necessarily match what the app requires now.

Side note - this kind of this is why good QA people are awesome. They'll show you what users will actually do.

I'll add in something here. Element the app said they were logging into matrix.org.

matrix.org has a "try matrix". The first thing is it tells me to choose a client (this feels like a loop), then says to choose a server but also maybe I don't need to, then has a create account button.

The create account button takes me to a docs page. Which tells me to go to the element site, and then create an account with matrix.

So that's matrix -> use element -> element says to use matrix -> matrix says to use someone else, ok you can use us -> to use us go to element -> element says you're making an account with matrix.

edit - oh you can and should also do this with your dev process.

Create an empty folder, check out the repo and follow the readme. Do you actually get a running system for local dev? Can you successfully run the tests? If you are able to, do this on a clean machine (maybe load up a docker image and see if you can follow it in a truly clear system). Does it turn out it assumes you already have tool X installed because your developers already have it from another project? Do you actually need postgres running with a specific user with specific login details?

If you're like me you don't like writing docs, so this may actually just push you to add scripts that do the setup required.

To not sound sanctimonious about this every time I've done this with my own code I've found issues with the documentation.