> [!tldr] **Increasingly concrete** It's good to know your values. Your principles make them actionable (because [[Principles are Verbs]]), and enumerating methods make them concrete. A good thing to think of as a group/hierarchically. Sort of a "why", "what", and "how" trio... sort of. _Note_: “methods” may also be constructed as “[[Guiding Principles|rules]]”. # Examples | Value | Principle | Methods | | :--------: | :------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- | | Charity | Give what you can to those who need it more | I will donate 25% of my bonuses and volunteer one day per quarter at XYZ shelter | | Simplicity | [[Do the Simplest Thing]] | I will favor plans with the fewest moving parts. I won't reinvent the wheel. I will apply the [[Pareto Principle]] rather than do it all. | ## ...Enter [[Disambiguating Principles and Best Practices|Best Practice]]s Somewhere between "methods" and "principles" would exist "**best practices**". They are more specific and discrete than principles, but probably less discrete and specific than what I'm calling methods up there. For more see [[Disambiguating Principles and Best Practices]]. For the sake of completeness, here's another table: | **Value** | Clarity | | ----------------- | --------------------------------------------------------- | | **Principle** | [[Make What's Important What's Obvious]] | | **Best Practice** | [[Establish Good Lifecycle Management Early]] | | **Method** | Create an "Archive" folder and rules around how its used. | **** # More ## Source - My own thinking and linking ## Related - [[Principles are Verbs]] - [[Value of General Operating Principles]] - [[5 Why to Your Values]] - [[Mission Statement]]