(Can We Craft a) Visual Explanation of the Process ?

[nelsonic]

Can we have a visual "workflow" of our process so people who aren't great with reading lots of text can grasp it in under 10 seconds?

@harrygfox / @iteles could we commission an infographic? which we could print A2 an have on the wall and also send to our remote collaborators and partners?

• https://www.peopleperhour.com/freelance/infographic+designer
• https://www.upwork.com/hire/infographics-freelancers/
• https://www.freelancer.com/jobs/infographics/1/

[iteles]

We should test and refine our process over the next 2 weeks and commission it then 👍🏻

[nelsonic]

@iteles that would require everyone to follow the process ... i.e. reading a lot of text ... 🐔 🐣 ❓

[jackcarlisle]

@iteles @nelsonic what about a visual process MVP? We could create a very simple diagram initially (draw.io?) and then once it's been tested and refined, commission the design of a higher quality one?

[iteles]

@nelsonic Right. But that tells us exactly what we need to highlight (i.e. what is less natural/instinctive).

@jackcarlisle Also really like that idea!

[nelsonic]

This is more required than ever before ...

[jackcarlisle]

@nelsonic If you gave me a sketch of exactly what you want the dwyl process infographic to look like (including detail on individual sections) I could design one relatively quickly

[nelsonic]

@jackcarlisle sadly, I'm "too busy" reviewing PRs to sketch the workflow ...
anyone else see the #irony here...?!?!

@iteles exactly one person who went to DWYL Summer bothered to read the contributing guide ... @Shouston3 ❤️ ... why not 100%?
Ensuring that everyone follows the steps (like "clockwork") is the single most important task
of a "Project Manager" otherwise my time is wasted "babysitting" on PRs
where simple process would avoid me having to keep asking:

• "What issue was this feature discussed in...?"
• "Please link to the issues in your PR description"
• "When was this requested by the Product Owner ...?"
• "Please update the documentation to reflect this new feature..."
• "Why does this test only check for a status code and not for functionality or content...?"
• "This PR is fixing a bug, why are there no comments or regression tests...?"
• "Please don't assign PRs for review until the build is passing and coverage is 100% ..."

like a broken-down-record-player ...! 😭

do people just not know about this doc? does dwyl have too many things for people to read...?

We could all work six-hour-days four-days-a-week remotely if everyone just had a clear understanding of and followed instructions ...

[nelsonic]

Re-opening as I think we should still have a (much better) diagram explaining the process...

[nelsonic]

It would be so awesome to have clear diagram explaining the "Workflow" used in all @dwyl projects/products ...
anyone want to volunteer to help craft it?