Adding larger-scope procedure design philosophies in the help section.
This idea is something that isn't pressing, but may help people learn how to save time in planning flows for entire projects from the ground up in a way that would make changing existing flows a whole lot easier.
It's been my experience that when a new project comes onboard, it will sometimes require a large set of flows and that planning is key to saving a whole lot of time when choosing which information to place in which flow, etc.
Something which I know your team knows very well is procedure creation methodology. My past KB experience has been mostly keyword search DB's to find articles, which gets bloated very quickly as one of the many downsides.
Thus I've started using a specific flow creation methodology. With a background in video game design, I was able to apply my knowledge of modular game design to PF creation when a set of flows need to be created asap (it involves several steps, planning being the equivalent of pre-production to create a minimal viable product, or in the case of an entire new entry flow with the bare necessities, with a list of fleshing them out with anything that isn't absolutely necessary for an agent to know to do a new duty).
Although I've seen the examples given by you on individual flow creation, to help people new to PF, perhaps adding a small write-up or some hyperlinks in your help section to some PF design best practices.
My personal experience is when I started applying the design planning methodology that I was most familiar with, it allowed me to plan an entire set of flows more efficiently, avoided redundancy, etc. Although perhaps not using my own methods, adding help resources may help people new to PF be more efficient at it (and not feel as overwhelmed as I was when I started using it and had to make a very large flow).
I know this is a wall of text, just trying to explain my idea so that you understand exactly what I mean.
-
This is an awesome idea! So far we have concentrated on Training the basics, then general conventions. But a methodology for tackling a large process would be really helpful to new people. We can't do this right away, but I am going to put some thought into doing a series and maybe we can start by posting it on the http://blog.procedureflow.com, then we can group them later into a web series people have access to. Thanks for the idea Jacques!