For Example If you consider Google Workspace is the product and Google Docs as a feature, how do you cover all the features of Google Docs in a single document?
I would not call this as a prd, it should be more of a vision doc on workspace as a product.
Docs as a prod would have some 5 to 10 different product teams working on it. It’s simply not logical to write one prd.
But if you do want to give it a shot: break down the feature into smaller components- instead of trying to cover everything in one document, break down the feature into smaller components. For example, for Google Docs, you could create separate sections for editing, formatting, collaboration, and sharing.
I had to make something similar in my previous org and what I did was similar, the product was a workspace and the doc was mostly a vision doc with intended users, impact, feature lists and roadmap I would hyperlink the feature lists with individual prds and we built a separate project on jira + confluence to better track progress
Use whimsical or draw.io to prepare a canvas first
@Tathastu can you elaborate a bit?
feeling like I am literally in the worst phase of my life. Our company is taking ownership of an abroad project and those abroad folks are not supportive or even if they support us then they give little information so that we can't take ...
I’ve worked at multiple orgs:
My tech team is blaming prds for delayed delivery of projects. But i am not sure if this is even a correct expectation. The design file had complete flows and written guidelines. Tech team said they wanted that level of clarity in the pr...
I recently transitioned from an intern to a FTE in a startup. I'm working on a SaaS product as an APM.
I have been taking up a lot of work, interacting with devs, QA, designers but neither do I feel that my manager notices what all I'm ...