AMPI PIC cheat sheet

Digital strategy maturity is assessed on four layers: data foundation, cloud infrastructure, AI/analytics capability, and operating model; a gap in any layer caps the value of the others.

Cloud economics rule: total cost of ownership compares on-premise capex plus 3-year run cost against cloud opex plus migration and exit cost; workload placement follows data gravity and latency, not fashion.

Data strategy sequence: define the business question, inventory sources, set ownership and quality SLAs, then build pipelines; governance precedes scale.

AI project viability test: a use case is viable when labelled or retrievable data exists, the error cost is tolerable, and a human review step can absorb residual risk.

Continuous updating requires a technology radar with four rings (adopt, trial, assess, hold) reviewed on a fixed cadence, typically quarterly.

Build-versus-buy decision rule: buy for commodity capability, build for differentiation tied to proprietary data or customer experience, and reassess at each major vendor release.

Pilot-to-production gate: a pilot scales only if it shows a measured baseline improvement, an owner, a funding line, and an integration path into existing systems.

AI governance minimum: model inventory, data provenance record, bias and drift monitoring, human escalation path, and documented decision rights.

Alliance value is measured by three tests: strategic fit with the roadmap, complementary capability rather than overlap, and a clear revenue or cost attribution model.

Network value follows weak-tie theory: novel information and referrals come disproportionately from acquaintances outside the immediate cluster, not from close colleagues.

Partner selection screen: capability gap, cultural and compliance compatibility, exit cost, and exclusivity terms; fail any one and the alliance carries structural risk.

Alliance governance needs a named executive sponsor on each side, a joint steering cadence, and a dispute escalation path written before launch.

Relationship maintenance rule: a professional network decays without contact; schedule touchpoints at least quarterly and log context so reconnection is specific, not generic.

Coopetition risk: when a partner is also a competitor, define data-sharing boundaries, IP ownership, and customer ownership in the agreement, not in conversation.

Ecosystem mapping: plot partners by influence and dependency; high-influence, low-dependency partners are the priority for proactive investment.

Value exchange principle: sustainable alliances deliver reciprocal benefit; a one-sided referral flow is a transaction, not an alliance.

Trust is built on three observable components: competence (delivered results), integrity (consistency between promise and action), and benevolence (demonstrated concern for the other party's interest).

Case study structure: context, problem, intervention, measured result, and transferable lesson; a case without a metric is an anecdote.

Result reporting rule: state the baseline, the metric, the measurement window, and the attribution method; percentage improvements without a baseline are unverifiable.

Best-practice adoption test: a practice transfers only when context similarity is high on scale, regulation, culture, and maturity; otherwise adapt, do not copy.

Trust recovery sequence after a failure: acknowledge specifically, explain cause without excuse, state the corrective action, and submit to verification.

KPI design principle: pair a leading indicator (adoption, cycle time) with a lagging outcome (revenue, retention) so results are visible before the quarter closes.

Case credibility check: independent verification, named client or anonymised sector, and a stated limitation increase trust; superlatives without evidence reduce it.

Feedback loop rule: results feed back into strategy on a fixed review cycle; a success case that is not re-examined becomes a stale template.

Usability heuristics to audit any interface: system status visibility, match to real-world language, user control and freedom, consistency, error prevention, recognition over recall, and clear error recovery.

Accessibility baseline is WCAG 2.2 level AA: contrast ratio of at least 4.5:1 for normal text, 3:1 for large text, keyboard operability, visible focus, and text alternatives for non-text content.

Core Web Vitals thresholds: Largest Contentful Paint at or under 2.5 s, Interaction to Next Paint at or under 200 ms, Cumulative Layout Shift at or under 0.1, measured at the 75th percentile.

UX research rule: five to eight participants per user segment reveal most usability problems in moderated testing; quantitative claims need a statistically sized sample.

Brand architecture choices: branded house, house of brands, and endorsed brands; the choice follows how much risk and equity transfer between products is desired.

Marketing funnel metrics: reach, engagement, conversion, retention, and referral; each stage has a distinct metric and a distinct optimisation lever.

Design-system value: a shared component library reduces inconsistency and build time; governance decides who can add or change components.

Message testing principle: test the proposition before the creative execution; a weak value proposition cannot be rescued by visual polish.