# Microsoft's Growth Mindset Principles

### Principle 1: Embrace Continuous Learning <a href="#principle-1-embrace-continuous-learning" id="principle-1-embrace-continuous-learning"></a>

Description: Foster an environment where team members are encouraged to learn new skills, acquire knowledge, and stay updated with industry advancements to drive innovation and personal growth.

#### Evaluation Criteria: <a href="#evaluation-criteria" id="evaluation-criteria"></a>

1. Engineers demonstrate continuous learning by actively pursuing educational opportunities, measured through participation in workshops and completion of relevant courses.
2. Team leads exhibit a growth mindset by encouraging team development, measured through the number of mentoring sessions conducted and learning resources shared.
3. Developers show commitment to learning by integrating new technologies into projects, measured through successful implementation and positive impacts on performance.

***

### Principle 2: Foster Resilience and Perseverance <a href="#principle-2-foster-resilience-and-perseverance" id="principle-2-foster-resilience-and-perseverance"></a>

Description: Encourage persistence in the face of challenges, viewing setbacks as opportunities for growth, and promoting a culture that values effort towards mastery.

#### Evaluation Criteria: <a href="#evaluation-criteria-.1" id="evaluation-criteria-.1"></a>

1. Engineers demonstrate resilience by persisting through difficult tasks, measured through successful resolution of complex issues and minimal escalation of problems.
2. Team leads promote perseverance by supporting team members during setbacks, measured through timely assistance and effective problem-solving strategies provided.
3. Developers show a growth mindset by adapting to feedback, measured through iterative improvements and responsiveness to code review comments.

***

### Principle 3: Encourage Open Feedback and Collaboration <a href="#principle-3-encourage-open-feedback-and-collaboration" id="principle-3-encourage-open-feedback-and-collaboration"></a>

Description: Promote a culture where constructive feedback is openly shared, and collaboration is encouraged to enhance team performance and individual development.

#### Evaluation Criteria: <a href="#evaluation-criteria-.2" id="evaluation-criteria-.2"></a>

1. Engineers demonstrate openness by actively seeking feedback, measured through regular participation in peer reviews and soliciting input on work products.
2. Team leads foster collaboration by facilitating inclusive discussions, measured through the frequency of team meetings and diversity of ideas implemented.
3. Developers show collaborative spirit by contributing to shared goals, measured through participation in cross-functional projects and collective problem-solving efforts.

***

### Principle 4: Value Effort as a Path to Mastery <a href="#principle-4-value-effort-as-a-path-to-mastery" id="principle-4-value-effort-as-a-path-to-mastery"></a>

Description: Recognize that consistent effort and dedication are essential for developing expertise and achieving excellence in engineering practices.

#### Evaluation Criteria: <a href="#evaluation-criteria-.3" id="evaluation-criteria-.3"></a>

1. Engineers demonstrate dedication by continuously improving their skills, measured through enhancements in code quality and adherence to best practices.
2. Team leads value effort by acknowledging team contributions, measured through recognition programs and positive performance feedback.
3. Developers show commitment by diligently working towards objectives, measured through timely task completion and willingness to tackle challenging assignments.

***

### Principle 5: Innovate Through Curiosity <a href="#principle-5-innovate-through-curiosity" id="principle-5-innovate-through-curiosity"></a>

Description: Encourage curiosity and questioning to drive innovation and creative problem-solving within the engineering team.

#### Evaluation Criteria: <a href="#evaluation-criteria-.4" id="evaluation-criteria-.4"></a>

1. Engineers demonstrate curiosity by exploring new solutions, measured through proposals of novel ideas and successful experimentation outcomes.
2. Team leads foster innovation by supporting creative initiatives, measured through resources allocated for research and the number of innovative projects launched.
3. Developers show creative problem-solving by applying unconventional approaches, measured through effective solutions that improve efficiency or performance.

***

### Principle 6: Cultivate Inclusive and Diverse Perspectives <a href="#principle-6-cultivate-inclusive-and-diverse-perspectives" id="principle-6-cultivate-inclusive-and-diverse-perspectives"></a>

Description: Promote an inclusive environment that values diverse viewpoints, enabling the team to make better decisions and create more effective solutions.

#### Evaluation Criteria: <a href="#evaluation-criteria-.5" id="evaluation-criteria-.5"></a>

1. Engineers demonstrate inclusivity by respecting different opinions, measured through positive peer interactions and collaborative success.
2. Team leads cultivate diversity by ensuring equal opportunities, measured through balanced task assignments and representation in decision-making processes.
3. Developers show openness by integrating feedback from various sources, measured through the diversity of contributions incorporated into their work.

***

### Principle 7: Take Ownership and Accountability <a href="#principle-7-take-ownership-and-accountability" id="principle-7-take-ownership-and-accountability"></a>

Description: Encourage team members to take responsibility for their work, owning both successes and failures, and learning from experiences to improve future outcomes.

#### Evaluation Criteria: <a href="#evaluation-criteria-.6" id="evaluation-criteria-.6"></a>

1. Engineers demonstrate ownership by proactively addressing issues, measured through the timely resolution of bugs and implementation of enhancements.
2. Team leads exhibit accountability by leading by example, measured through transparent communication and acceptance of responsibility for team deliverables.
3. Developers show responsibility by learning from mistakes, measured through adjustments made after retrospectives and reduction in repeat issues.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.aude.ai/aude-product-documentation/goals/performance-categories/microsofts-growth-mindset-principles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
