Content Strategy Research Roadmap (Doc Ops (How often will products be…
Content Strategy Research Roadmap
What does a good template look like?
Who should review?
Should doc be housed with code? What's best practice?
What tools are available to standardize API documentation?
How are APIs documented for each PROS product currently?
Who is the primary audience for API documentation?
What do they use this documentation to do?
What do we currently integrate with? (By product)
Are there any similarities in our current integration docs? Could we create a template?
[PPSS] What is the best way to present Tech Note information?
[Travel] Where to put Connectors documentation?
How do Cloud and IT teams currently decide how to configure their environments?
Who writes tech config doc?
Do they work from a template? Is there any standardization?
What do runbooks look like? What information do they contain?
What information do cloud v. on-prem customers need re: technical config?
Who's responsible for creating this doc?
Maintaining this doc?
Where is this documentation housed? Internally or externally?
How do we currently document system architecture?
Who at PROS understands system architecture?
What information do customers need to know about architecture?
What does good architecture doc look like?
Business User Help
What features of in-app help do we appreciate in other products?
What information we currently publish in Connect should be translated in-app?
What tools are available for in-app help? What options are free? Which require dev time?
Best Practices Examples
What use cases are needed for each product?
What does a helpful use case look like?
What are we (PROS) sharing as best practice information?
What does Challenger sales model provide as business cases?
Who knows best practices at PROS? For each product?
How is best practice information best consumed?
How do users currently decide how to set up their system for their business scenario?
How often will products be releasing in new DevOps process?
What does DevOps process look like from a dev perspective? Cloud perspective?
Are releases managed differently in DevOps world?
How are versions handled in PROS DevOps world? Do versions mean anything?
What support do on-prem customers require? What's MVP in cloud-optimized world?
What release processes are automated w/ Dev Ops?
What are DevOps leads responsible for? What information do they need to meet responsibilities?
Who's responsible for ensuring docs get updated with new feature info?
What does workflow look like?
Who reviews current documentation for accuracy/usefulness?
How do we determine what information is out of date?
Is there a way to automate review cycles? What would a good system look like?
What feedback should we seek regarding documentation quality?
How would we solicit that feedback?
Where will we collect that feedback?
Who will be responsible for feedback?
Graphics, Video, Design
Do we have any standard images we use?
Where are they housed?
How does PROS represent systems graphically? What are the standards?
What are marketing design standards?
Do we meet marketing design standards (colors, etc.) in doc?
What tools make systems image generation simpler? What's out there?
How is internal information gathered?