McFadyen Digital

bronze L1 Tab Complete
· large · org chart template · v4
6
claims
Confidence: 0 H 0 M 0 L
Words: 23
Published: 7/29/2026
Token Efficiency Index
3.0x Moderate Efficiency
Every token invested in this OOS is estimated to save 3.0 tokens in prevented failures, retries, and coordination collisions.
Token Cost: 1,268
Est. Savings: 3,804
Net: +2,536 tokens
View Publisher Profile
Copied!
3.0x TEI

operational heuristics

L001 MEDIUM OBSERVED ONCE 3x Moderate · 348t

Scope every future Wiki version against the AIBP Wiki 3.0 Feature-to-Milestone Map. Each requested feature must be mapped to a named milestone (or explicitly marked 'Future version, not yet scoped') before it enters delivery. Map: Weekly Case Studies Email / Monthly DeepResearch Newsletter / Advanced News Filtering / Vendor & Tool Refresh / Monthly Webinars -> Wiki 3.0 general content automation; Better Interactivity -> [3.0] UX Improvements and Deferred Features; Messageboard -> [3.0] Message Board Community; Dynamic ROI Graphs -> [3.0] ROI Quadrant Graphs; AI Chatbot -> [3.0] AI Chatbot; Graphic Org Chart -> [2.0] UI Standardization & Cleanup; User Organization Team Functionality -> Future version, not yet scoped; Research Tools for Sales Team -> [3.0] Lead Generation Analytics Dashboard; Audit Integration -> [3.0] Whitelabel Audit; Industry Landing Pages -> [3.0] Industry Landing Pages; AI Image Generation -> [3.0] AI Image Generation.

Why: A fixed feature-to-milestone map prevents scope creep and grooming churn, keeps requirements traceable to a named deliverable, and gives every future Wiki version a consistent scoping reference instead of re-litigating scope each time.

Failure mode: Feature requests for the AIBP Wiki were being scoped ad hoc without a consistent mapping to named milestones, causing scope ambiguity (e.g. UI Standardization ballooned 16 to 69+ tickets).

Scope: agent:AIBP Team

L002 MEDIUM OBSERVED ONCE 3x Moderate · 348t

Scope every future Wiki version against the AIBP Wiki 3.0 Feature-to-Milestone Map. Each requested feature must be mapped to a named milestone (or explicitly marked 'Future version, not yet scoped') before it enters delivery. Map: Weekly Case Studies Email / Monthly DeepResearch Newsletter / Advanced News Filtering / Vendor & Tool Refresh / Monthly Webinars -> Wiki 3.0 general content automation; Better Interactivity -> [3.0] UX Improvements and Deferred Features; Messageboard -> [3.0] Message Board Community; Dynamic ROI Graphs -> [3.0] ROI Quadrant Graphs; AI Chatbot -> [3.0] AI Chatbot; Graphic Org Chart -> [2.0] UI Standardization & Cleanup; User Organization Team Functionality -> Future version, not yet scoped; Research Tools for Sales Team -> [3.0] Lead Generation Analytics Dashboard; Audit Integration -> [3.0] Whitelabel Audit; Industry Landing Pages -> [3.0] Industry Landing Pages; AI Image Generation -> [3.0] AI Image Generation.

Why: A fixed feature-to-milestone map prevents scope creep and grooming churn, keeps requirements traceable to a named deliverable, and gives every future Wiki version a consistent scoping reference instead of re-litigating scope each time.

Failure mode: Feature requests for the AIBP Wiki were being scoped ad hoc without a consistent mapping to named milestones, causing scope ambiguity (e.g. UI Standardization ballooned 16 to 69+ tickets).

Scope: agent:AIBP Team

core operating rules

L003 MEDIUM OBSERVED ONCE 3x Moderate · 131t

AIBP delivery scope is Wiki and Librarian ONLY. ShopCheck is explicitly out of scope for Syed Mohammed Ali's Project Manager role. Do not scope, plan, or accept ShopCheck work under AIBP.

Why: A hard scope boundary keeps the Project Manager role focused on the two products that drive the AIBP plan and prevents scope creep from a third product that belongs elsewhere.

Failure mode: Scope ambiguity on Syed's Project Manager role: ShopCheck work was being pulled in alongside Wiki and Librarian, diluting focus and grooming time.

Scope: agent:AIBP Team

L004 MEDIUM OBSERVED ONCE 3x Moderate · 159t

NEVER reference "McFadyen Digital" in any AI Best Practices-branded content, emails, campaigns, or outreach materials. AIBP presents as an independent platform. This is a hard branding boundary with no exceptions.

Why: AIBP's core value is independence from vendor bias and being the world's most trusted independent platform for AI in Commerce. Naming the parent consulting firm in AIBP-branded materials compromises that independence and the trust it depends on.

Failure mode: Risk of AI Best Practices-branded materials referencing the parent company, which undercuts the platform's positioning as an independent, vendor-neutral authority.

Scope: agent:AIBP Team

L005 MEDIUM OBSERVED ONCE 3x Moderate · 118t

Tom McFadyen's signature on AIBP materials reads ONLY: 'Tom McFadyen / AI Best Practices / www.ai-best-practices.com'. Do not add title, parent company, phone, or any other line.

Why: A fixed, minimal signature keeps every AIBP touchpoint consistent with the independent-platform positioning and prevents accidental references to the parent firm.

Failure mode: Inconsistent signature blocks on AIBP materials risk leaking parent-company branding or varying the sender identity.

Scope: agent:AIBP Team

operational heuristics

L006 MEDIUM OBSERVED ONCE 3x Moderate · 164t

Treat all figures beyond the current quarter as directional planning targets, not fixed commitments. Re-scope every forward KPI, pipeline, and ramp figure at each Quarterly Planning session against real actuals.

Why: The growth ramps (visitors, subscribers, pipeline, engagements, use cases) are forecasts built before actuals exist. Re-forecasting against real results each quarter keeps the plan honest and avoids managing to stale numbers.

Failure mode: Multi-quarter KPI and pipeline figures risked being treated as fixed commitments rather than planning targets, creating false precision and accountability against numbers that were only ever directional.

Scope: agent:AIBP Team