Phronesis

The goal of the "Phronesis" training is not only to deepen your understanding of our products but also to empower you to contribute actively to their enhancement and evolution. Read about what we expect from each student.

How it works

To ensure the training runs smoothly and everyone is clear on the structure, here are the logistics:

• Teams: Each participant is paired with a colleague (by the Team Picker). Pairs will be predetermined and persist for one cycle duration. If a teammate is out of office, substitutions may occur.

• Schedule: The training cadence is weekly. Please be punctual and collaborate with your partner to ensure full participation.

  When to work	Description
  Strict	All teams work on the same day
  Flex	Work to complete the training within the specified timeframe

  Way to work	Description
  Meld	One "screen" and one "keyboard"
  Sync	Work at the same time without screenshare
  Staggered	Work separate hours (one might wait for a notification to do a review)

• Priority: This training is a priority for our team development and product enhancement. As such, all regular work assignments will be adjusted to accommodate your participation in the training. Think about training like the highest p1 priority. A p0 (such as an outage) is more important.

• Resources provided: You will have access to all necessary technical documentation, tools, and access rights to our products. This includes detailed guides on how to use Reunite and Realm effectively within different contexts presented in the training.

• Support: Throughout the training, you will have continuous support from your pairing partner and our product experts. Should you have any questions or require technical assistance, please do not hesitate to reach out in the #phronesis slack channel.

This structure should help set clear expectations and provide a detailed roadmap for the logistics of the "Phronesis" training program, ensuring that all participants are well-prepared and the training objectives are met effectively.

Phronesis origins

The name "Phronesis" was chosen for this training program to embody the essence of practical wisdom and ethical understanding. Phronesis is a term from ancient Greek philosophy, primarily discussed by Aristotle. It refers to the ability to determine the most suitable course of action in a given situation. Unlike theoretical knowledge (episteme), phronesis encompasses the practical application of intelligence, wisdom, and virtue towards making decisions that align with good character.

Origin of the word:

• Greek roots: The word "phronesis" comes from the Greek verb "phronein," which means 'to think,' 'to consider,' or 'to have understanding.' In philosophical terms, it implies not just any thinking, but thoughtful, reflective consideration about how to live well.
• Philosophical context: Aristotle described phronesis as a key virtue that is crucial for achieving 'eudaimonia,' or flourishing, which he considered the highest human good. In his Nicomachean Ethics, phronesis is depicted as the virtue that enables individuals to navigate complex moral landscapes with insight and to act virtuously.

Why Phronesis for training? Naming our training program "Phronesis" reflects our commitment to nurturing not only technical skills but also the judicious application of these skills in real-world scenarios. It emphasizes our belief in the importance of wisdom, critical thinking, and ethical decision-making in the development of software and technology. By invoking the concept of phronesis, we encourage all participants to aspire to practical wisdom as they interact with and enhance our products.

This connection to philosophical wisdom sets a profound tone for the training, inspiring participants to engage thoughtfully and meaningfully with the material and their work.

Phronesis admin

While everyone drives phronesis forward as a student, there are a few special roles that help design, organize, and summarize learnings from the training.

Project ideas

Do you have ideas for a training project?

Are you planning on releasing a new product feature?

We should release features like this:

1. Prepare feature and docs.
2. Make release candidate.
3. Prepare training project that uses release candidate and rc-docs.
4. Review feedback from training.
5. (Optional) Make minor adjustments and go to step 7.
6. (Optional) Make major adjustments and go back to step 1.
7. Release.

You can educate the entire company about your new product feature and at the same time get valuable feedback.