-
Notifications
You must be signed in to change notification settings - Fork 0
Recipes index
Arlo Belshee edited this page Oct 28, 2013
·
2 revisions
@kentsu66: The editor in me REALLY wants to change the title to sentence case, but I can’t figure out how — it’s apparently seen as trying to create a new file with the same name.
We have three categories of recipes:
- Assessment recipes help you identify your team’s current level(s) of interaction by scope.
- General-purpose recipes help you improve your overall level of interaction. They make your team better.
- Special-purpose recipes help you solve a particular problem. You pick them by the pain point you are feeling, and they cure that one ill.
Both sets of recipes are open-ended. Please add more. If you wish to add your recipe to this list, contact @arlobelshee. Better yet, send a pull request.
Recipe | Notes |
---|---|
Fluency examples | Assesses the degree to which you have fluent proficiency at each level. |
Purpose | Recipe | Notes |
---|---|---|
Improve all aspects | Road to collaboration | A coordinated path to improve across all three contexts at once. |
Improve my team internally | Improve my team | aka “Get your own nest in order” Takes you all the way along the road from your current level of interaction to full Collaboration. |
Improve interactions with partner teams | Improve partner relations | aka “Make friends” Getting aligned with each of your key partner teams about what level of interaction is needed pays big dividends. |
Learn to work out loud | Working out loud | aka “Influence people” Casting a net for new partners within your wider organization seem daunting but it’s actually easy to get started, and it’s hard to go wrong. |
Contributing to others | Working with the loud | How to work well with a team that is working out loud and contribute to their success – without having to expend much of your time. |
Supporting anonymous learning | Anonymous learning | A hubs and spokes approach. How to identify the sets of information for which you could be a hub. How to be a successful hub. How to be a succcessful spoke and learn from other hubs. |
Scope | Level | Pain point | Recipe | Notes |
---|---|---|---|---|
Within team | ? | Friction caused by style differences | SPR-Understanding problem-solving styles | Basadur Creative Problem-solving Profile |