What is the primary objective of using the I2A2 playbook design methodology?

Question

Options

• ATo create simple, reusable, modular playbooks.
• BTo meet customer requirements using a single playbook.
• CTo create detailed playbooks.
• DTo create playbooks that customers will not edit.

• A
  88% (28)
• B
  3% (1)
• C
  6% (2)
• D
  3% (1)

Explanation

Option A is correct because the I2A2 methodology (Identify, Investigate, Act, Automate) emphasizes building playbooks that are simple (easy to understand and maintain), reusable (applicable across multiple scenarios), and modular (broken into discrete, interchangeable components) - core design principles that maximize flexibility and long-term value.

Why the distractors are wrong:

• B is wrong because I2A2 deliberately avoids single-monolithic playbooks; modularity means tasks are split across multiple focused playbooks that can be combined as needed.
• C is wrong because detail is secondary to simplicity and modularity - overly detailed playbooks become brittle and hard to reuse.
• D is wrong because I2A2 playbooks are meant to be adapted; the methodology encourages customer ownership and customization, not locked-down artifacts.

Memory tip: Think of I2A2 playbooks like LEGO bricks - small, simple, reusable pieces you snap together to build anything, rather than one giant pre-built model you can't change.

No community discussion yet for this question.