As a transitional step, this site will temporarily be made Read-Only from July 8th until the new community launch. During this time, you can still search and read articles and discussions.

While the community is read-only, if you have questions or issues requiring TIBCO review/response, please access the new TIBCO Community and select "Ask A Question."

You will need to register or log in or register to engage in the new community.

Example subject hierarchy for early tibbr rollouts

Last updated:
11:55am Mar 21, 2017


Further below is one example of a generic subject hierarchy for tibbr. tibbr's subject structure is completely customizable and flexible, so perhaps consider this a starting point or example to broaden the vision of what a subject structure might look like early on in a planned rollout. tibbr subjects can easily be moved, renamed, etc., so our advice is to start simply and evolve the subject hierarchy as needed.  

Also, attached at the bottom of this web page is a general best practices guide for thinking about creating/evolving your subjevt hierarchy.

General Approach

If you are using tibbr to help distribute, consume, and create feedback and next steps on analytics insights such as Spotfire, then teh subjects you create will necessarily be oriented in that direction. Or if you're collaborating mainly around some new professional services project, or external community for customers, then of course your subject structure will be direcly relevant to that. In either case, think about what kinds of conversations your organization wants to elicit and build on, and create subjects grouped to help with that. For example, if you're launching collaboration for internal collaboration, then in the following departments, you might want to setup subjects that pertain to the goals sampled below:

•  Management: Walk the virtual halls of your organizations for dynamic feedback.
•  Sales: Securely engage everyone helping close the deal: Pre-Sales, Marketing, Finance, etc.
•  Marketing: Increase the speed of responding to RFPs with wider and easier coordination.
•  Support: Better handle exception cases by scaling expertise, and preserving the decisions.
•  Production/Manufacturing: Share best practices on inventory management.
•  Finance: Simplify monthly accounting close by synchronizing the steps in a private subject.
•  Human Resources: Collect internal referrals from employees who know a great candidate.

Example Subject Structure

With these ideas in mind, here's what the subject structure might look like:

  • Communications & News
    • Crazy New Ideas
    • Industry News
    • Loudspeaker
    • Water Cooler
  • Initiatives
  • Products
  • Regions & Sites
    • Americas
    • APJ
    • EMEA
  • Teams & Projects
    • Project X Team (By Approval)
    • Program Management Office (Private)
    • Departments
      • Administration & FInance
        • Accounting
        • Facilities
      • Customer Success
      • Engineering
        • Development
        • QA
        • Release Management
      • Human Resources
      • Marketing
      • Product Management
      • Sales
      • Technical Support
  • tibbr Help

There is no right and wrong; but rather creating a subject structure is mainly a matter of what to emphasize. This subject structure can be changed at any time, and new subjects are simple to add.

Let us know if you have any questions, and be sure to visit the tibbr Customer Success Center for more ideas and best practices!


PDF icon tibbr_subject_best_practices.pdf2.92 MB