We ensure a solid foundation, provide guard rails, structure data, and information architecture (IA).
Example: Someone requests to add webinars as a new functionality on the website. We should ask follow up questions about how they’re planning to use these and what their needs are for the short term and the long term. We provide structure that enables (or at least doesn’t hinder) the long term goals such as URL pathing, related IA, templates, components, descriptions for CMS input fields, etc.
We don’t create content, but we’re responsible for how content gets implemented. To use resources efficiently, we want to enable self-service content creation.
Example: Someone wants to add webinars as a new functionality on the website. We might build CMS fields with descriptions and instructions for how to use them. We might also provide necessary tools such as markdown, WYSIWYG, image uploads, video embeds, form embeds, etc. We should gather feedback about these tools so we can iterate and improve them.
We provide directional input. We have ideas about where the object could go, should go, should not go, and how to get there.
Example: Someone wants to add webinars as a new functionality on the website. We should understand what’s possible in a given timeframe, what resources are available, if there’s a good business case to prioritize this, and what projects might provide more impactful results if we worked on them first. This doesn’t typically include project management. Rather it includes tasks, roadmaps, and OKR planning from a contributor’s perspective.
We advise stakeholders and contributors about things like best practices, user behavior, page speed, return on investment, technical requirements, historical performance, etc.
Example: Someone wants to add webinars as a new functionality on the website. We might advise what updates the website could need before, during, and after a webinar. We can also advise what are best practices for webinar landing pages and conversion.