Milestone map
Milestone map
2 milestones
Do the exercises and show your work
7–14 weeks (4 hrs/week)
Take Organizational Behavior for free and do the chapter questions and cases (motivation, teams, conflict, power, culture, change). Keep your answers in one public place (a repo, a shared folder or a page) as you go, with your reasoning shown.
Proof required
Link your public folder with the chapter questions and cases (motivation, teams, conflict, power, culture, change), and show your self-check (Organizational Behavior: end-of-chapter questions).
What gets checked
- Case answers use a named model correctly.
- Each answer says what the model cannot explain.
- Review questions are checked against the key.
Common mistakes
- Answers copied from a key: verifiers read the reasoning.
- Numbers with no working.
- Asking for review before the self-check.
Powstik Guide
A public folder with your worked answers to the chapter questions and cases (motivation, teams, conflict, power, culture, change).
Steps
- Make a public folder or repo for this course.
- Do one chapter or problem set at a time and save it.
- Self-check: Answer each chapter's review questions before you read the answer. Where the book gives an answer key, mark yourself against it; for the rest, check each answer against the chapter text and note the section. Write down what you got wrong.
- Fix what the self-check shows, and say what you fixed.
- Ask three people who know the topic to check it.
Template
README Course: Organizational Behavior (OpenStax Organizational Behavior (free book)) What is here: Self-check result: The hardest question and why:
What gets sent back
- Answers with no working.
- Self-check not shown.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Case answers use a named model correctly.
- Each answer says what the model cannot explain.
- Review questions are checked against the key.
- Pick two answers and check every step.
- Ask about one step; the answer should be clear.
You'll sign in first, then come straight back here.
Run a four-week team log
1–3 weeks (5–8 hrs/week)
Use what you learned. Make a four-week log of a real group you belong to (decisions, conflict, motivation), applying two models from the course, and a change you tried with the result. Put it where verifiers can open it. Use public information, or data you have permission to use; never publish a real person's private details.
Proof required
Link a four-week log of a real group you belong to (decisions, conflict, motivation), applying two models from the course, and a change you tried with the result, and a short note on what you decided or changed because of it.
What gets checked
- There is an entry for each week, written at the time.
- The two models are applied correctly.
- The change and its result are reported honestly, including if it failed.
Common mistakes
- Invented or unsourced figures.
- A conclusion the evidence does not support.
Powstik Guide
A four-week log of a real group you belong to (decisions, conflict, motivation), applying two models from the course, and a change you tried with the result.
Steps
- Write one line: what you will show.
- Gather the real data, people or documents.
- Draft it, then read it cold the next day.
- Ask someone to mark the first claim they doubt.
- Fix it and ask three people to check it.
Template
Title: What this shows: Sources: Method: Result: Limits:
What gets sent back
- Unsourced numbers.
- Not clearly the person's own work.
- Claims more than it shows.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- There is an entry for each week, written at the time.
- The two models are applied correctly.
- The change and its result are reported honestly, including if it failed.
- Check that the work is the person's own and the sources are real.
- Ask how a number was found.
You'll sign in first, then come straight back here.