Reflection
This Confluence site might be one of my greatest representations of utilizing all of my skills in one body of work. Confluence is itself a collection of documents, filters, searches, and nifty add-ons for tailored
functionality. I built every space (sort of an individual site or wiki), page, process, etc., in collaboration with customers or teams within the company. Templates were created by working with the individual requester or team.
For example, if the Marketing and Sales team requested a scenario mapping template, I would research examples (templates) and meet with the requestor(s) to analyze their needs. After making some revisions and publishing it with their
approval, we would then work to incorporate the template into their team space (such as adding a button that would create a new page from a template).
To develop wikis within Confluence, I had to work with individuals and teams to identify and respond to their situations/requirements. However, community buy-in wasn't readily available. However, I didn't have a readily available
process for taking the multiple repositories and organizing them.
This WYSIWYG wiki tool was intended to help solve the organization's communication and archival-related problems. Most employees were aware of these issues (more or less) but couldn't spare the time to change. Bringing light to these
issues is where collaborating to address team/individual needs became so important. Individuals need to have the opportunity to provide feedback - to have buy-in or "skin in the game." If I assumed their needs based on existing
structures or searchable templates, their team could end up with useless documents and processes they will never utilize. By meeting with the team or individual to identify their needs, I can review industry standards to tailor a
solution.