Product Management

Redocd providesĀ UnderstandingĀ to your Product team. To provide understanding, Flashpages were built to allow your team to easily manage Products, and their associated features.

A cross-functional Product team is typically comprised of the following types of roles, although they may be different for your company. And some of these roles can be combined or expanded depending on your business needs. However, a standard agile product team will have these basic roles:

Ā 

  • Product Owner builds the stories and prioritizes (e.g. Jira)
  • Tech Lead (Architect)maps out a process Storyboard (e.g. Visio)
  • Designer builds a Wireframe and/or Mockups (e.g. Zeplin)
  • Developer builds the software (e.g. Github)
  • Tester writes the tests cases (e.g. Zephyr, Jira)

Redocd makes Product Management simple for everyone. Let’s use the ‘Designer’ role for this use case:

After developing mockups for a new feature, your designer first has to share them with the team. Redocd makes this simple by making the folder the user uploads to most auto-pinned to the first position. Here, a designer can first simply ‘dump’ all his/her mockups for several different features in one spot. (Note: Linkshares to mockups are supported, like Figma, Invision or Zeplin):

A Mockups folder on a Propage

Looking at the image above, you will see that when a file is hovered, you can see which feature(s) they belong to.  But for simplicity sake, any file can be uploaded without being associated to a feature (flashpage).

Once the Designer uploads their mockups, he/she needs to ‘publish’ them to the correct Flashpage. The Flashpage is the published page for any new feature. Therefore, using our team configuration above, there will be a deliverable from each team member including the Designer. To associate a mockup(s) with a flashpage, the Designer simply needs to hover over the card, and use the flashpage dropdown. He/she could instead simply drag the card to the correct feature in the list to the right.

Once in the flashpage, you will see on the right-side of the flashpage a folder called ‘Mockups’. Only the files the Designer tagged with this feature (e.g. ‘Client Portal’ feature) will be visible here. This makes for easy publishing, so the Designer doesn’t have to re-add the same mockups to the published feature page that he/she already added to their Mockups folder.

The Designer could also have done the reverse. If he/she uploaded their mockups directly to the flashpage, a pop-up will appear asking which folder to associate the files to. This is even quicker than before, as it allows the Designer to upload once, and move the file to the correct published feature page (flashpage) and upload directly to their mockups folder at the same time.

 

Adding files directly to a flashpage allows a User to move the file to two locations at one time: the project folder, and the feature page.

Once your team has created one feature, it’s easy to simply repeat the process. Using the Clone button, the current feature (flashpage) can be used as a template for the next feature.

Cloning a flashpage (a published feature)
Once a flashpage is cloned, the folder structure is retained. This allows your team to easily upload and linkshare directly to the next feature your team will work on.

No more needing to create templates; your previous flashpage is your template. You can see that the folder structure is retained for the next feature. Move quickly with flashpages and help your team easily share and publish their deliverables with the team.