Storefronts Use Case

Video created by brianna.walsh Employee on Aug 3, 2020

    Storefronts Use Case

    Thanks for joining this session on the Storefront Use Case. This session continues on from where we left off in the Information Architecture session and assumes that you have a good understanding of Jive. If you are new to Jive and have not reviewed the Jive Basics and Managing Places sessions, in addition to the information architecture one, please do so before this one.

     

    First, let’s review the definition of a storefront: a Jive place where official content lives. We recommend using spaces for storefronts because they can be permissioned so that only the content owners can create and update the official content, and all (or a majority) of employees can view and comment, or ask questions. Another benefit of using spaces only for storefronts is that the orange space icon becomes identifiable to users as official, or intranet, places.

     

    1. The first step in developing your info architecture was to identify the top-level topics - and as part of this, estimate how much content would be related to these topics and sub-topics. Now, as you are preparing to begin working in your storefront spaces, you’ll want to finalise these content counts by creating a content inventory which includes a list of any content that already exists, but also content that might need to be created. It might look something like this, with columns for the name of the content, the owner or author, the kind of content it is - like a video or PDF file, the sub-topic if any, whether to update, keep, delete or create the content, and the tags it should have:Migrating content to Jive offers a rare opportunity to retire outdated content. As you are doing the inventory, decide which content needs to be uploaded into Jive - and only move what is absolutely necessary. We recommend delegating this task to the content owners/managers for the topic. They know the content the best - and are the best judges of what is needed to be on the intranet.
    2. Once you have a content inventory completed for each of your Phase 1 topics, you may find that you need to adjust your site architecture plan based on the decision tree for categories and subspaces.
      • If you are planning on including official/corporate news and announcements in any of your storefronts, be sure to review the Communications Use Case session as well.
      • If there is not a lot of content for the top-level topics - or they don’t meet any of the other criteria for having a space - consider combining related topics. Remember: the less hierarchy and places to maintain, the better for both content owners and users!
    3. Now is the best time to start building your structure. You might be tempted to get started before you get to this step. And there is no reason that you can’t change the structure within Jive if you’ve already created some spaces. We find, though, that if you do all of this work outside of the platform first, the actual implementation goes much faster within Jive.
    4. Once you have the spaces created, it is time to think about the user experience for the landing pages of the storefronts. A consistent layout and tile placement is key to making it easy for users to quickly know where to look for the same information. For example, an ask tile should always be placed in the top left position. Or, a helpful links tile with links to external tools is always in the middle of the right rail. This doesn’t mean that you should militantly force all landing pages to have exactly the same tiles - if there is no content to fill one of them, don’t use it. But if you are going to have an ask a question tile on the landing page, be sure that it is in the same position on the page in every storefront.[snippet break]
    5. Now let’s go to the front end of Jive and look at the first space you created. Using the method of your choice, go to the space. As we learned in the Managing Places sessions, the default for a new place is the Activity page. But for a storefront, you’ll want to create at least one custom tile page - there tends to be a lot of content that needs to be surfaced on storefront landing pages.
      • As a reminder, click the Manage cog in the banner and select Create a Page from the dropdown.
      • For storefronts, we recommend using a 3-column layout so that most of the information you are sharing will be “above the fold” for desktop users.
    6. Let’s look at an example of how your landing page(s) might look once it’s fully configured.
      • Use banner icons that give a visual cue to what the place is about and a banner that matches your corporate branding.
      • Include a combination of calls to action using curated/static tiles and dynamic “signs of life” tiles like the superlist tile or recent blogs tile.
      • But, your landing page should not be used to display every piece of content that lives in the storefront space. Keep it as simple as possible while giving users the pointers to what they need most often.
      • When deciding on the tiles to use, the thing that you want mobile users to do first should be in the top left position. Consider that if you don’t want them asking questions before they browse for what they need, you may not want to put the ask tile there. However, if you want to encourage them to use that functionality before scrolling down the page, this is the perfect place to put it
      • Commonly used elements for storefront landing pages are:
        • Categories tile for sub-topics
        • Key content and places tile for sub-space navigation or for surfacing important content
        • But another option is to use a banner tile with images that link to either of these - this will make the landing page more engaging
        • Helpful links tile for links to external tools and platforms
        • Ask a question tile and a corresponding superlist tile filtered only on questions. The reasons for keeping these two tiles as a “package deal” are several: 1. Before asking the question, users can see if their question has already been asked and answered by looking at the list in the tile, 2. when they create a question, they want to see it on the landing page so they know that it’s there, and 3. The community manager for the storefront can easily see the unanswered questions that need to be addressed without having to click on the content tab. Keep in mind that if you are going to include the possibility of users asking questions, there must be someone who will answer them promptly - or else users will continue to email or phone with the same question over and over again.
        • If you are using this storefront for official news and announcements, the recent blogs tile will display the most recent ones
        • Superlist tile filtered and sorted to show the most recently updated documents - this is one of those “signs of life” tiles that will reassure users that this is a vibrant, active storefront
        • Featured user tile (I like “who can help” as a title) which displays the people who are in charge of this storefront
      • Finally, weigh the amount of time it takes to maintain a pixel-perfect landing page with the number of users who may actually be navigating to the landing page. Many users will use the search functions or get to the content within the storefront in other ways.
    7. If you have multiple sub-topics for your storefront topic and have decided to use categories for them, you also have the option of creating up to 4 more custom tile landing pages (as covered in the Managing Places sessions).
      • For example, in your Working at the Company storefront, you might want to give users an easy way to see all content related to Employee Benefits on one page, all content related to Learning and Development on another, and perhaps all content related to Corporate Policies on yet another. This also allows you to create different calls to action for each sub-topic.
      • Another way that these pages can be effective is to make them role-based - as in this example. The content may be available to all users, but packaging it differently for different audiences can make it easier for them to identify what is most important. For example, on the New Joiners page, you might create a checklist which includes all the things they need to do in their first weeks.
    8. Once you have a good idea of the structure of the storefront, hide the place navigation elements that may be confusing to users, such as the Activity page and the Subspaces and Projects page. Do this by again clicking the Manage cog and selecting Navigation. Reminder: this is also where you go to re-order the pages you’ve created.



    We recommend building out the “Working at the company” space before you start the others. This gives you a chance to “work out the kinks” first. Load or create enough content in the space so that you can see how the dynamic tiles will look. Add the appropriate images to any banner or other image tiles. Then adjust as necessary before finalising your “template” for the other storefronts.

     

    Once you are happy with how this first storefront is shaping up, you can start to build out the rest of the storefronts. If you have delegated this to the future place owners (which we recommend doing), it is a good idea to give them some training and guidelines about how you have chosen to implement the storefronts in your community. Include a wireframe outlining the tiles and their position on the storefronts, and the naming conventions you are using.

     

    Thank you for joining this session today. If you will be posting official news and announcements for this topic, please review the Corporate Communications use case session before you finalise your template.