Work, work, I could do using Confluence as I use it right now.( Trick) I like to keep two backlog lists: Confluence is a great tool to support ways of working that you are refining over time. ( Trick) As you get smarter about using the tools, touch up the stuff you did before.
This is the approach you and Kesha are taking above. When one looks useful, try it with something you are doing. ( Trick) Start with some little bit of work you are doing that would be useful to record, retrieve, share and track. ( Trick) Think of Confluence as a weird kind of file cabinet on steroids. I'm poking around and am having a hard time knowing where to start. For example, if you work more project based, maybe you have a parent page that is:ĭoes that help answer your question? Let me know if I'm not understanding correctly! OR your parent page can be related to what the process is for. as parent pages and underneath you have your different processes and specs. The page tree organization can work the same way with Processes, Tech specs, etc. In this space is where you keep all documentation relevant to your team's schedule, workflows, processes, etc. you can really set it up the same way, but I'd do it in a separate IT team space. In that space, we have setup the page tree hierarchy to be parent page for the topic and then child pages underneath that go into detail on the subtopics:įor the documentation that's more to be consumed by you and your team on specs, processes, etc.
For example, we have a Workplace Technology space that is purely for the whole company to refer to if they have questions about process, systems, software, etc. If you have docs that are being written to be consumed by those outside your team then I'd create a space specifically for those docs. Got it - so it looks like there may be a mix of docs that are just relevant to your team and some that are relevant to your customers/employees (whoever your users are)?