Pivot or persevere meeting

From Pearl Language
Revision as of 15:40, 24 August 2015 by Martien (talk | contribs) (Zeroth version.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

…product experiments show decreasing effectiveness and there is a general feeling that product development should be more productive.

✣  ✣  ✣

{{{wish full}}}

The decision to pivot;

  • requires a clear-eyed and objective mind-set.
  • is emotionally charged and requires a structured approach; therefore
    • schedule the meeting in advance;
    • schedule a regular pivot or persevere meeting every six to nine weeks;

Therefore:

Call for a gathering to decide to pivot or persevere. Include participation of at least people from product development and business leadership. Include perspectives from outside advisers who help see past preconceptions and interpret data in new ways. Have the product team bring a complete report of its product development…

✣  ✣  ✣



✣  ✣  ✣