Search by property

Jump to navigation Jump to search

This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.

Search by property

A list of all pages that have property "So" with value "Grow a system, don't build it.". Since there have been only a few results, also nearby values are displayed.

Showing below up to 11 results starting with #1.

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)


    

List of results

  • Daily clean code  + (Fix all bugs in less than a day. Aim to have a completely clean base of code at the end of every day.)
  • First things first  + (Focus maximum effort to get the top priority ready to release and celebrate yet another ka-ching moment.)
  • Tipping point leadership  + (Focus on three factors of disproportionate influence in motivating employees—kingpins, fishbowl management, and atomization.)
  • Tribal learning  + (Form a triad of tribal leadership based on aligned values where each person is responsible for the quality of the relationship between the other two.)
  • Spectrum of views  + (Form subgroups that listen to each other’s conversations to discover differences that can be integrated.)
  • Six plus or minus one  + (Foster teams of six plus or minus one so they excel in communication saturation and collective team knowledge.)
  • Pen storm  + (Generate a number of ideas and leave some white space in between for the others to embellish and augment.)
  • 3 × 3 rule  + (Get any three levels and any three functions into the same conversation on any issue of mutual concern.)
  • Whole elephant  + (Get out all the issues, find out what matters most, and only then explore any solutions and directions to resolve one or more issues.)
  • Time to express yourself  + (Give people time to come to grips with their feelings before focusing on action.)
  • Agile team dōjō  + (Guide and coach the team through an intense weekly training program.)
  • Lazy finish  + (Hand-off the request to another party where it can later be retrieved and completed.)
  • Daily standup  + (Have a short inspect-adapt meeting, that lasts at most 15 minutes, every day.)
  • Focus on focus off  + (Have everyone compare words like inquiry/advocacy, dialogue/debate, conversation/argument, their meaning, and how they impact behavior.)
  • Back brief  + (Have others brief what they think has just been said back to the sender so you can check if the intent is well understood; clarify when needed.)
  • One service deserves another  + (Have the product owner crew decide which build squad will pull this item into their sprint backlog.)
  • Allies experience differences  + (Identify differences, make them heard, involve everyone, create subgroups exploring and integrating the differences.)
  • Scrumming the scrum  + (Identify the single most important accelerator at the Sprint Retrospective and remove it before the end of the next sprint.)
  • Weak signals, big action  + (Improve your situational awareness and take big action when weak signals elude danger.)
  • Whole system in the room  + (In each meeting, include all the relevant people who “ARE IN” .)