The Rule of Three
/ Stephanie FamuyideI came, I saw and I conquered.
These few words of Julius Caesar provide a good example of the Rule of Three.
The main idea behind the Rule of three is that concepts presented in threes are easy to remember. An interesting benefit that comes from applying the rule of three is that others will remember what you have to say and so will you.
A real-life application is this: when structuring your presentation, group your ideas or key takeaways into groups of three so that it’s easier for your audience to remember them. The key is to always ask yourself at every point: If your audience is only going to remember 3 things from this presentation, what should they be? The Rule of three can prevent you from getting stuck in the middle of a presentation if you deliver your points in threes.
It might not always be ideal to split your ideas into groups of three, after all, the world is certainly more complex than the number 3. In some cases or most (depending on how talkative you are :), you will certainly have more to say than 3 sections will allow. In that case, regroup your ideas into 3 higher level concepts that will allow you to deliver the main points succinctly. The Rule of 3 is certainly not applicable in all situations but can be useful in:
- Remembering concepts
- Delivering speeches and
- Setting goals.
Use this list of 3 to remember when to apply the rule of 3.
Data mining can be described as the process of improving decision-making by identifying useful patterns and insights from data.
A data dictionary holds data about the fields in a database, such as field definitions, meanings and allowable values that reflect how data is used within a domain or organization.
Are you a business analyst involved in the documentation of business rules and creation of complex decision tables?
A concept model provides a great way of documenting definitions and communicating precise meanings of terms to stakeholders.
Employing the user journey mapping technique involves adopting a user-centric approach to product design, revealing opportunities to delight customers and identifying pain points that can be addressed thereby creating a product with an improved user experience.
Within the context of agile software development, the product backlog is a platform where all the potential work (product backlog items) that need to be delivered are recorded, tracked and prioritized. Though owned by the Product Owner, anyone may suggest items to add to it.
Failure Mode and Effects Analysis (FMEA) is a proactive technique that can be applied to the early detection of failures or defects in products and services. It is a systematic risk assessment process used by analysts looking to reduce the chances of faults by detecting problems and their possible repercussions in time for remediation.
If you are in business, here is a brief overview of how cause and effect analysis helps you find viable business solutions. Guest post by Lucas Cappel.
A roles and permissions matrix, an audit requirement in some organizations, is used to ensure that business activities are covered by identifying the responsibilities and roles linked to them.
Business Process Model and Notation (BPMN) is a global standard for constructing process models, with more organizations using it and schools teaching it as a subject.
User story maps are an interesting and collaborative way of eliciting user requirements. One of the reasons why I find it so powerful is because it provides a unique approach for aligning discussions relating to the user, their goals, the process that supports the accomplishment of their predefined goals; and the requirements that need to be addressed to solve business problems.