Feedback on Planual

Options
David_Hu
David_Hu Member, ALL USERS, GroupMember Posts: 4 New Contributor
in Anaplan Community

I attended Live User event last Thursday. David Smith presented tips and tricks from The Planual (the official model-building guidebook). I am wondering its update cycle and feedback collection channel. Below are a few my wish items:

1. Impact based rule grouping: The Zen of Anaplan is a good start. I feel it will even better by consolidating ten guidelines to a few guiding principles (i.e. simple is beauty, minimum calculation, go natural with Hyperblock engine). Then cast down to high impact guidelines and rules. Second part is also raised by one of audience.  

2. New UX best practice:  Given new UX pulling data across models by new designated role (meaning new users other than model builders), it provides benefits while could introduces new implications. For example, should module pick is limited to output/input ones only? 

3. Admin best practice: The issues I was facing in recent admin transition experience indicate governance and guidelines are needed in this area. In addition, workspace partition and usage are relevant model life cycle and performance management talked in Planual. Noticed recent monitoring ecosystem topics is also relevant with this. 

 

What are your thoughts on this topics?

Comments

  • David_Hu
    David_Hu Member, ALL USERS, GroupMember Posts: 4 New Contributor

    Clarify #2 New UX best practice.

    Agree with you 'UX Principle' stays the same. Most of rules in 'UX Built' can also be shared.

    So New UX best practice is sort of additional focus on the new use cases new UX brings:

    1. New UX intends to free model builder load by creating a new role 'New UX builder' to handle UX portion. It provides benefits while requires model design more flexible anticipating future needs (vs. back to first design). It is interesting how to set module access boundary for 'New UX builder' role.

    2. New UX enables to pull modules across multiple models by different model builders. It provides benefits to free data export/import across models. I am wondering whether it bring implications when sync and presentation consistence are part of requirements. 

Categories