/* ========================================================================== HomeRefined.jsx — @role Home section sub-components (hero, breaks-down cards, methodology, etc). Loaded BEFORE HomeMinimal; HomeMinimal reuses these globals. Components share global scope (no imports). ========================================================================== */ /* PSL Home — refined, section-by-section improvement of mayers-club.webflow.io Same outline, same sections, same copy intent. Tighter type, hierarchy, density, visual treatment. PSL-only naming (consistent with Diagnostic). */ const HArrow = ({ size = 16 }) => ; const HCursorClick = ({ size = 16 }) => {/* cursor pointer */} {/* click radiating arcs */} ; /* ===================================================================== 01 — HERO Existing: Audience photo · purple overlay · long question headline. Refinements: - Tighter type scale, slightly smaller headline so the supporting line can breathe and the CTA row reads as the actionable hero. - Two CTAs: Primary teal (Take Diagnostic) + ghost (Start a conversation). Promotes the diagnostic which is the actual next-step. - Eyebrow tag added for orientation. - Subline (free / 7 min / report) lifted into a meta row of icon chips so the trust signals are more legible than a single grey line. - Stat callout (10+ / 25+ / 70%) folded into hero base for a stronger first impression — currently it's a separate band that reads weak. ===================================================================== */ const HRefined_Hero = () =>
; /* ===================================================================== 02 — CREDIBILITY STATS BAND Was: a moving marquee of client logos sitting between the hero and the dark "Where Performance Breaks Down" section. Now: a static credibility stat band on the off-white background. The client logos themselves have been promoted into the hero (see .hr-hero-trusted in HRefined_Hero). One credibility moment per section — the logos belong with the hero, the numbers belong here. ===================================================================== */ const HRefined_Stats = () => { const stats = [ { n: "10+", l: "years leading complex delivery" }, { n: "25+", l: "organisations engaged" }, { n: "70%", l: "measurable execution lift" }]; return (
{stats.map((s) =>
{s.n}
{s.l}
)}
); }; /* ===================================================================== 03 — WHERE PERFORMANCE BREAKS DOWN Existing: dark bg · "Where Performance Breaks Down" headline · three numbered statements stacked left, photo right · only #2 is "active". Refinements: - Convert the "only #2 active" pattern into a deliberate carousel-style focus pattern with three indexed states and a clearer storytelling structure: the eye lands on the active item, the others are the before/after framing. - Photo right is preserved but with a stronger composition — added a small overlaid "live" annotation chip pointing at the central problem, so the image earns its place. - The supporting paragraph below the headline is rewritten to be stronger and shorter. ===================================================================== */ /* Three illustrations, one per "breaks down" card. Activated by hover/click. */ const BreaksIllustration = ({ active }) => { // common defs reused across all three scenes const Common = () => ; // SCENE 01 — pressure rising faster than absorption const Scene01 = () => CADENCE OF DEMAND 2024 ▸ NOW {/* horizontal grid */} {[80, 130, 180, 230].map((y, i) => )} {/* incoming pressure waves — accelerating frequency */} {[ { x: 60, h: 60, c: "rgba(244,114,182,0.5)" }, { x: 95, h: 80, c: "rgba(244,114,182,0.6)" }, { x: 132, h: 100, c: "rgba(244,114,182,0.7)" }, { x: 168, h: 120, c: "rgba(244,114,182,0.8)" }, { x: 200, h: 140, c: "#F472B6" }, { x: 228, h: 160, c: "#F472B6" }, { x: 254, h: 175, c: "#F472B6" }, { x: 278, h: 185, c: "#F472B6" }, { x: 300, h: 195, c: "#F472B6" }, { x: 320, h: 200, c: "#F472B6" }, { x: 338, h: 200, c: "#F472B6" }, { x: 354, h: 200, c: "#F472B6" }, { x: 368, h: 200, c: "#F472B6" }, { x: 380, h: 200, c: "#F472B6" }]. map((b, i) => )} {/* capacity ceiling — flat */} CAPACITY {/* breach callout */} DEMAND BREACH POINT {/* time arrow */} TIME ; // SCENE 02 — effort up, throughput flat (existing) const Scene02 = () => WEEK 01 WEEK 12 {[80, 130, 180, 230].map((y, i) => )} {[[32, 220], [110, 175], [195, 130], [290, 90], [395, 65], [448, 60]].map(([x, y], i) => )} {[[32, 175], [150, 176], [290, 176], [448, 175]].map(([x, y], i) => )} EFFORT THROUGHPUT DIVERGENCE ; // SCENE 03 — capacity reservoir draining as intensity stays high const Scene03 = () => Q1 Q2 Q3 Q4 {/* horizontal grid */} {[80, 130, 180, 230].map((y, i) => )} {/* intensity line — pink, sustained high then crash at end */} {[[32, 90], [180, 72], [330, 78], [395, 145], [448, 215]].map(([x, y], i) => )} {/* capacity reservoir — descending fill bar bottom area */} {/* labels */} INTENSITY RESERVES {/* collapse callout at end */} COLLAPSE ; return ( {[...Array(96)].map((_, i) => { const cols = 16; const x = 32 + i % cols * 28; const y = 32 + Math.floor(i / cols) * 28; return ; })} {active === 0 && } {active === 1 && } {active === 2 && } {/* bottom team avatar row — common across all scenes */} {[ "assets/headshot-1.webp", "assets/headshot-2.jpg", "assets/headshot-3.jpeg", "assets/headshot-4.jpg", "assets/headshot-5.jpeg", "assets/headshot-6.jpeg"]. map((href, i) => )} {[64, 132, 200, 268, 336, 404].map((x, i) => { // Per-scene team-health pattern: each member has a fixed bar width + color // representing green (healthy), amber (strained), red (critical). const G = "rgba(46,224,176,0.85)"; const A = "rgba(245,158,11,0.85)"; const R = "rgba(239,68,68,0.85)"; const scenes = [ // Scene 01 — pressure rising: most still green, two amber, one tipping red { widths: [22, 19, 16, 12, 22, 18], colors: [G, A, A, R, G, A] }, // Scene 02 — effort up, throughput flat: spread across all three states { widths: [21, 13, 18, 10, 22, 15], colors: [G, R, A, R, G, A] }, // Scene 03 — reserves draining: mostly amber/red with one green hold-out { widths: [20, 12, 8, 14, 9, 6], colors: [G, R, R, A, R, R] }]; const w = scenes[active].widths[i]; const color = scenes[active].colors[i]; const headshots = [ "assets/headshot-1.webp", "assets/headshot-2.jpg", "assets/headshot-3.jpeg", "assets/headshot-4.jpg", "assets/headshot-5.jpeg", "assets/headshot-6.jpeg"]; return ( ); })} ); }; const HRefined_BreaksDown_v1 = () => { const items = [ { n: "01", t: "Pressure is increasing faster than your team's ability to absorb it.", d: "AI adoption, regulated transformation, cloud migration. The cadence has changed; the operating system underneath the team has not." }, { n: "02", t: "Your team is busy, but delivery keeps stalling.", d: "Most teams are working hard. The problem is not motivation — it's that the system underneath the work is not structured to hold under sustained pressure. Priorities shift, dependencies pile up, and delivery becomes unpredictable despite high individual effort." }, { n: "03", t: "High performance is being sustained through intensity alone — and it is starting to show.", d: "Senior people are absorbing what the system cannot. It works for one quarter, maybe two, then capacity collapses." }]; const [active, setActive] = React.useState(1); return (

Where performance breaks down.

Most approaches to performance were designed for stable environments. When pressure does not let up, effort alone stops being enough. Performance problems are not people problems — they are systems problems. Here's where the system typically gives.

{items.map((it, i) => )}
{["Pressure rising · capacity flat", "Effort up · throughput flat", "Intensity high · reserves draining"][active]}
Illustration · Replace with brand-supplied photography or motion at production time.
); }; /* Simplified, typographic version. Lighter visual load; reads at a glance. To revert: render or in root. */ const HRefined_BreaksDown_v2 = () => { const items = [ { n: "01", t: "Pressure is increasing faster than your team's ability to absorb it.", d: "AI adoption, regulated transformation, cloud migration. The cadence of demand has changed; the operating architecture underneath the team has not." }, { n: "02", t: "Your team is busy, but delivery keeps stalling.", d: "The problem is not motivation. The system underneath the work is not designed to hold when priorities shift and dependencies pile up. Effort stays high, output stays inconsistent." }, { n: "03", t: "High performance is being sustained through intensity alone \u2014 and it is starting to show.", d: "Senior people are absorbing what the system cannot. It works for a quarter, maybe two. Then capacity collapses." }]; return (

Where performance breaks down.

Most approaches to performance were designed for stable conditions. When pressure does not let up, effort alone stops being enough. Performance problems are not people problems — they are architecture problems. Three patterns appear repeatedly.

{items.map((it, i) =>
{it.n}

{it.t}

{it.d}

)}
); }; /* ===================================================================== 04 — PSL PERFORMANCE SYSTEM Existing: white bg · long-form intro · big rings graphic on left · three domain blocks stacked on right (Performance Identity, Execution Architecture, Sustainable Capacity) with an "active" highlight that the user couldn't easily switch between. Refinements: - The rings stay (key brand asset). Make them sticky/large. - Three domain rows beside them become an interactive switcher: clicking a row highlights the corresponding ring. The current pattern has the interaction without the affordance — add the affordance. - Tighter intro: lead with the verdict, not two paragraphs. - Each domain row gets a kicker line ("WHO YOU ARE / HOW THE WORK GETS DONE / WHAT FUELS IT") — currently exists but very faint. ===================================================================== */ const HRefined_System = () => { const domains = [ { id: "identity", t: "Performance Identity", k: "WHO YOU ARE UNDER PRESSURE", d: "Values, standards, and behavioural anchors that determine how individuals and teams make decisions when conditions are difficult. Without a designed performance identity, standards default under pressure rather than hold." }, { id: "execution", t: "Execution Architecture", k: "HOW YOU TURN INTENT INTO CONSISTENT ACTION", d: "The decision-making, prioritisation, and delivery flow that turns leadership intent into shipped work. When the architecture is wrong, effort multiplies and output stays flat." }, { id: "capacity", t: "Sustainable Capacity", k: "HOW YOU MAINTAIN INTENSITY WITHOUT BREAKING", d: "The recovery, load management, and adaptability design that allows performance to continue under sustained pressure. Without sustainable capacity, intensity becomes the ceiling rather than the foundation." }]; // ring data-ring → domain index. "architecture" = execution pillar. const ringToIdx = { identity: 0, architecture: 1, capacity: 2 }; const idxToRing = ["identity", "architecture", "capacity"]; const [committed, setCommitted] = React.useState(0); const [preview, setPreview] = React.useState(null); const active = preview !== null ? preview : committed; const ppsRef = React.useRef(null); React.useEffect(() => { const el = ppsRef.current; if (!el) return; let fired = false; const trigger = () => {if (fired) return;fired = true;el.classList.add('is-in');}; if ('IntersectionObserver' in window) { const io = new IntersectionObserver((entries) => { entries.forEach((e) => {if (e.isIntersecting) trigger();}); }, { threshold: 0.35 }); io.observe(el); return () => io.disconnect(); } trigger(); }, []); // Hover preview only on real mouse — touch falls through to click/commit. const onPointerEnter = (idx) => (e) => {if (e.pointerType === 'mouse') setPreview(idx);}; const onPointerLeave = (idx) => (e) => {if (e.pointerType === 'mouse') setPreview((p) => p === idx ? null : p);}; const onFocusPreview = (idx) => () => setPreview(idx); const onBlurPreview = (idx) => () => setPreview((p) => p === idx ? null : p); const commit = (idx) => () => {setCommitted(idx);setPreview(null);}; const onRingKey = (idx) => (e) => { if (e.key === 'Enter' || e.key === ' ') {e.preventDefault();setCommitted(idx);setPreview(null);} }; const ringClass = (base) => base; return (
{/* Two-row layout: Row 1 — head text on the left · rugby photo on the right Row 2 — rings illustration on the left · domain cards on the right Each row uses the same 1.05fr / 1fr split so the column gutter lines up vertically and the whole section reads as a 2×2 grid. */}
THE PSL PERFORMANCE SYSTEM

We rebuild the structure underneath. So performance is driven systematically.

Identity Execution Capacity Performance

Elite sport learned long ago that performance under pressure is not produced by effort — it is produced by design. Identity, execution, and capacity, designed and rehearsed before the contest. The PSL Performance System brings the same three domains into executive delivery. When all three are aligned, performance becomes consistent.

{/* First visual reference to sport on the page — paired with the text on the right, so the metaphor lands the moment the copy first names it. */}
A rugby lineout — players lifted to contest the ball against an open sky.
From elite sport The lineout — coordinated lift, rehearsed timing, contested pressure. Performance under load is decided before the contest, not in it.
CAPACITY ARCHITECTURE IDENTITY
{domains.map((d, i) => )}
The three domains are not independent. Identity without Execution produces aspiration. Execution without Capacity produces short-term output at long-term cost. The system only holds when all three are designed to work together.
); }; /* ===================================================================== 05 — BUILT ON PROVEN PRINCIPLES Existing: off-white · centred eyebrow + headline · three card columns (Real Delivery / High-Performing Teams / Elite Performance). Refinements: - Cards keep the left brand-blue rule (signature visual cue). - Add a single supporting figure to each card: a domain anchor ("From the field" / "From research" / "From sport") to make the three sources of truth more legible. - Tighten body copy to one paragraph each — current is slightly long. - Add a subtle citation footnote per card so it earns its place. ===================================================================== */ const HRefined_Principles_v1 = () => { // Field — overlapping calendar/programme cards (delivery cycles, work in flight) const FieldIcon = () => ; // Research — concentric data rings with a centre node (research / convergence) const ResearchIcon = () => ; // Sport — runner mid-stride on a track (elite performance, conditioning) const SportIcon = () => {/* head */} {/* torso */} {/* front (lead) leg — bent, knee high */} {/* back leg — driving off */} {/* front arm — pumping forward */} {/* back arm — driving back */} {/* track lanes — curved */} ; const items = [ { tag: "FROM SPORT", t: "Elite Performance Environments", c: "RING-TESTED METHOD", Icon: SportIcon, theme: "violet", b: "In boxing, a fighter's performance in the ring is the direct product of how the fight camp was designed — preparation cycles, recovery discipline, identity stability, composure under consequence. The same architecture applies to senior delivery work. PSL adapts the principles that produce repeatable performance in elite sport for environments where the contest is corporate and the pressure is sustained." }, { tag: "FROM RESEARCH", t: "High-Performing Teams Research", c: "MCKINSEY · PROJECT ARISTOTLE", Icon: ResearchIcon, theme: "mint", b: "McKinsey's work on organisational health and Google's Project Aristotle on team effectiveness independently point to the same conclusion: sustained team performance is a property of the operating system, not of individual talent." }, { tag: "FROM THE FIELD", t: "Real Delivery Experience", c: "10+ YEARS", Icon: FieldIcon, theme: "blue", b: "Grounded in over a decade of leading complex delivery programmes across financial services, global retail, and enterprise technology. Whether the team runs Agile, waterfall, or hybrid, the pattern of where performance breaks down is consistent — and structurally addressable." }]; return (
BUILT ON PROVEN PERFORMANCE PRINCIPLES

Drawn from sport. Validated by research. Proven in delivery.

The PSL Performance System is not a theoretical model. It draws on three sources that have each been pressure-tested independently — and converge on the same structural conclusions about how performance is produced under sustained load.

{items.map((p) =>
{p.tag}

{p.t}

{p.b}

{p.c}
)}
); }; /* ===================================================================== 06 — WHERE DO YOU WANT TO START? Existing: white · two cards (For Individuals / For Teams & Organisations) · single CTA "Take the Performance Assessment". Refinements: - Cards become two coloured gradient cards (matching the Diagnostic page's routing pattern — same visual language across pages). - Each card has its own CTA (was: shared CTA below). - "Choose your path" decorative side anchors removed. Centred headline + cards keeps it cleaner. - Time labels on each card (~7 min / ~10 min) for self-routing. ===================================================================== */ /* MERGED — Final CTA + Routing combined on dark navy. The narrative reads: "either it holds or it doesn't" → "here are the two paths to start" */ const HRefined_Routing = () =>
START WITH THE DIAGNOSTIC

Your performance system either holds under pressure, or it doesn't.

The diagnostic takes around 7 minutes. It shows you exactly where the system is strongest, and where pressure is most likely to find the gaps. Free, structured, and the clearest starting point for building performance that holds.

Not sure which path? Both diagnostics share the same three-domain framework — start with whichever scale you operate at most.
; /* ===================================================================== 07 — FINAL CTA Existing: dark purple bloom · "Your performance system is either designed to hold under pressure, or it is not." · two CTAs. Refinements: - Sharper composition: a vertical brand mark or rings echo on one side so the strip is more than a centred wall of text. - Smaller secondary CTA (link style) so the primary teal CTA is unambiguous. - Trust line moved into the panel to reinforce free / structured. ===================================================================== */ const HRefined_FinalCTA = () =>
START WITH THE DIAGNOSTIC

Your performance system is either
designed to hold under pressure,
or it is not.

The diagnostic takes around 7 minutes. It shows you exactly where the system is strongest, and where pressure is most likely to find the gaps. It is free, structured, and the clearest starting point for building performance that holds.

; /* ===================================================================== 08 — FAQ Existing: "Your Questions, Answered" · centred · 5 items. Refinements: - Two-column: heading + contact prompt left, accordion right (matches Diagnostic page pattern for cross-page consistency). - Slightly tighter Q copy. ===================================================================== */ const HRefined_FAQ = () => { const items = [ { q: "What is the PSL Performance System?", a: "It is the three-domain framework — Performance Identity, Execution Architecture, Sustainable Capacity — together with the diagnostic, coaching, and embedded engagement work used to redesign each domain. We treat performance as one structural system, not three separate offers." }, { q: "How is this different from coaching or consulting?", a: "Both, integrated. PSL designs the system and embeds the work. Conventional coaching addresses the individual; conventional consulting redesigns process. PSL operates at the layer underneath both — the structural system that decides whether either holds under pressure." }, { q: "How do I know if PSL is right for my team or organisation?", a: "Start with the free diagnostic. 7 minutes, structured PDF report by email. The diagnostic locates the primary constraint in your performance system and tells us — and you — whether the next step is coaching, team-OS redesign, or an organisational engagement." }, { q: "Who is this for?", a: "Senior technology leaders, delivery owners, and individual contributors operating under sustained pressure: AI adoption, regulated transformation, cloud migration, complex programme delivery. PSL is calibrated for professional and corporate contexts." }, { q: "What happens after I take the diagnostic?", a: "You receive a structured PDF report by email with scores per domain and your primary constraint. From there, you can act on the recommendations, retake the diagnostic in 6–12 weeks to measure shift, or engage PSL on the paid Comprehensive Diagnostic which includes an executive readout and a recommendation plan scoped to your environment." }]; const [open, setOpen] = React.useState(0); return (
FAQ

Your questions, answered.

If your question isn't here — or you'd like to talk through whether PSL is the right fit for your environment — reach the team directly.

{items.map((it, i) =>
{i === open &&
{it.a}
}
)}
); }; /* Engagement vignette — long prose version (kept for revert). To revert: render in root. */ const HRefined_CaseStudy_v1 = () =>
ENGAGEMENT IN FOCUS

A critical cloud migration. Delivered on time, on track, without heroics.

PSL was engaged on an enterprise cloud migration where a critical workstream was at risk of slippage. The constraint was not capability — the people were capable. The constraint was structural: dependencies tangled, ownership unclear, operating rhythm reactive.

We restructured the delivery teams, redesigned the dependency map, and put a deliberate operating rhythm underneath the work. The team delivered on the date originally committed, with minimal downstream impact, and without escalation rescues from senior leadership.

{[ { n: 'On time', l: 'Critical workstream delivered to the date originally committed.' }, { n: 'On scope', l: 'No reduction of intended outcomes despite sustained pressure.' }, { n: 'Minimal drag', l: 'Dependencies resolved structurally, not reactively.' }, { n: 'Sustained', l: 'No reliance on senior heroics or weekend rescue work.' }]. map((s, i) =>
{s.n}
{s.l}
)}
; /* ===================================================================== INSIGHTS v1 — three-card grid. Preserved for revert. New v2 below. ===================================================================== */ const HRefined_Insights_v1 = () => { const articles = [ { tag: 'SUSTAINABLE CAPACITY', t: 'Recovery Is Inevitable. The Only Question Is Whether It Is Planned.', read: '9 min read' }, { tag: 'EXECUTION ARCHITECTURE', t: 'Heroics Are Not A Strategy. They Are A Symptom.', read: '8 min read' }, { tag: 'PERFORMANCE IDENTITY', t: 'What Standards Are For (And Why Yours Default Downward).', read: '7 min read' }]; return (
FROM THE LAB

Recent thinking on performance under pressure.

Read all insights
{articles.map((a, i) => {a.tag}

{a.t}

{a.read}
 )}
); }; /* ===================================================================== BREAKS DOWN v3 — three navy cards, watermark numbers, subtle motifs. Preserved for revert. New v4 below. ===================================================================== */ const HRefined_BreaksDown_v3 = () => { const items = [ { n: "01", label: "PRESSURE", t: "Pressure is increasing faster than your team's ability to absorb it.", d: "AI adoption, regulated transformation, cloud migration. The cadence of demand has changed; the operating architecture underneath the team has not.", accent: "#F472B6", motif: }, { n: "02", label: "DIVERGENCE", t: "Your team is busy, but delivery keeps stalling.", d: "The problem is not motivation. The system underneath the work is not designed to hold when priorities shift and dependencies pile up. Effort stays high, output stays inconsistent.", accent: "#FBBF24", motif: }, { n: "03", label: "COLLAPSE", t: "High performance sustained through intensity alone \u2014 and it is starting to show.", d: "Senior people are absorbing what the system cannot. It works for a quarter, maybe two. Then capacity collapses.", accent: "#EF4444", motif: }]; return (

Where performance breaks down.

Most approaches to performance were designed for stable conditions. When pressure does not let up, effort alone stops being enough. Performance problems are not people problems — they are architecture problems. Three patterns appear repeatedly.

{items.map((it) =>
{it.n}
{it.label}
{it.motif}

{it.t}

{it.d}

)}
); }; /* ===================================================================== CASE STUDY v2 — tighter prose, structured C/R/O inset, weighted chips Preserved for revert. New v3 below. ===================================================================== */ const HRefined_CaseStudy_v2 = () =>
ENGAGEMENT IN FOCUS

A critical cloud migration. Delivered on time, on track, without heroics.

An enterprise cloud migration where a critical workstream was at risk. The constraint was structural — not capability.

{[ { label: 'CHALLENGE', accent: '#F472B6', body: 'A critical workstream slipping in an enterprise cloud migration. Capable people, structurally constrained \u2014 tangled dependencies, unclear ownership, reactive operating rhythm.' }, { label: 'RESPONSE', accent: '#9CA3FF', body: 'Restructured the delivery teams. Redesigned the dependency map. Installed a deliberate operating rhythm underneath the work.' }, { label: 'OUTCOME', accent: '#7FE7C8', body: 'Delivered on the date originally committed. Minimal downstream impact. No senior escalation rescues. The workstream proceeded as a clean line, not a series of fires.' }]. map((row, i) =>
{row.label}
{row.body}
)}
{[ { n: 'On time', l: 'Delivered to the date originally committed.' }, { n: 'On scope', l: 'No reduction in intended outcomes under pressure.' }, { n: 'Minimal drag', l: 'Dependencies resolved structurally, not reactively.' }, { n: 'Sustained', l: 'No reliance on senior heroics or weekend work.' }]. map((c, i) =>
{c.n}
{c.l}
)}
; /* ===================================================================== BREAKS DOWN v4 \u2014 dark navy cards w/ watermark numbers (current). Preserved for revert. New v5 below. ===================================================================== */ const HRefined_BreaksDown_v4 = () => { const items = [ { n: "01", label: "IDENTITY", sub: "Where standards live", t: "Standards quietly default under pressure.", d: "When the team's behavioural anchor isn't deliberately designed, performance habits drift downward under load. Quality bars slip a percentage at a time \u2014 until \"how we do things\" has quietly become something else.", accent: "#F472B6", motif: }, { n: "02", label: "EXECUTION", sub: "Where intent becomes action", t: "Effort multiplies. Output does not.", d: "When the underlying flow isn't designed, priorities drift, dependencies pile up, and shipped output thins out \u2014 even as everyone works harder. Heroic compensation hides the structural fault.", accent: "#FBBF24", motif: }, { n: "03", label: "CAPACITY", sub: "Where the reserves live", t: "Intensity becomes the system. Then it isn't.", d: "When recovery and load aren't structured, senior people absorb what the system cannot. It works for a quarter, maybe two. Then engagement thins, decision quality drops, and capacity collapses without a visible failure point.", accent: "#EF4444", motif: }]; return (

Where performance breaks down.

Most approaches to performance were designed for stable conditions. When pressure does not let up, effort alone stops being enough. Performance problems are not people problems — they are architecture problems, and they appear in three specific places.

{items.map((it) =>
{it.n}
{it.label}
{it.sub}
{it.motif}

{it.t}

{it.d}

)}
); }; /* ===================================================================== CASE STUDY v3 \u2014 action-titles per C/R/O row + quiet 2x2 chips (no bar) Preserved for revert. New v4 below. ===================================================================== */ const HRefined_CaseStudy_v3 = () =>
ENGAGEMENT IN FOCUS

A critical cloud migration. Delivered on time, on track, without heroics.

An enterprise cloud migration where a critical workstream was at risk. The constraint was structural — not capability.

{[ { label: 'CHALLENGE', accent: '#F472B6', title: 'A workstream slipping under pressure.', body: 'A critical workstream inside an enterprise cloud migration was at risk of slippage. The people were capable \u2014 but the dependency map was tangled, ownership was unclear, and the operating rhythm was reactive to events rather than ahead of them.' }, { label: 'RESPONSE', accent: '#9CA3FF', title: 'Rebuilt the structure underneath.', body: 'We restructured the delivery teams to match the work, redesigned the dependency map to remove blocking sequences, and installed a deliberate operating cadence \u2014 daily flow, weekly architecture, monthly performance \u2014 underneath the delivery.' }, { label: 'OUTCOME', accent: '#7FE7C8', title: 'Delivered as a clean line.', body: 'The workstream landed on the date originally committed, with no senior escalations and minimal downstream impact. Delivery moved as one continuous line, not a series of fires \u2014 and the change in operating rhythm held after the engagement closed.' }]. map((row, i) =>
{row.label}

{row.title}

{row.body}

)}
{[ { n: 'On time', l: 'Delivered to the date originally committed.' }, { n: 'On scope', l: 'No reduction in intended outcomes under pressure.' }, { n: 'Minimal drag', l: 'Dependencies resolved structurally, not reactively.' }, { n: 'Sustained', l: 'No reliance on senior heroics or weekend work.' }]. map((c, i) =>
{c.n}
{c.l}
)}
; /* ===================================================================== INSIGHTS v2 \u2014 editorial list (no cards). Preserved. New v3 below. ===================================================================== */ const HRefined_Insights_v2 = () => { const articles = [ { tag: 'SUSTAINABLE CAPACITY', t: 'Recovery Is Inevitable. The Only Question Is Whether It Is Planned.', read: '9 min read' }, { tag: 'EXECUTION ARCHITECTURE', t: 'Heroics Are Not A Strategy. They Are A Symptom.', read: '8 min read' }, { tag: 'PERFORMANCE IDENTITY', t: 'What Standards Are For (And Why Yours Default Downward).', read: '7 min read' }]; return (
FROM THE LAB

Recent thinking on performance under pressure.

Read all insights
); }; /* ===================================================================== CASE STUDY v4 \u2014 warm cream, before/after visual (preserved). New v5 below — cool palette, brand colors. ===================================================================== */ const HRefined_CaseStudy_v4 = () => { const stats = [ { n: "100%", l: "On-time delivery", d: "Committed date held." }, { n: "100%", l: "Scope protected", d: "No reduction under pressure." }, { n: "0", l: "Senior escalations", d: "Resolved structurally." }, { n: "0", l: "Weekend rescues", d: "No reliance on heroics." }]; const rows = [ { label: "CHALLENGE", accent: "#DB2777", title: "A workstream slipping under pressure.", body: "A critical workstream inside an enterprise cloud migration was at risk. The people were capable \u2014 the dependency map was tangled, ownership was unclear, and the operating rhythm was reactive to events rather than ahead of them." }, { label: "RESPONSE", accent: "#1F4DD8", title: "Rebuilt the structure underneath.", body: "We restructured the delivery teams to match the work, redesigned the dependency map to remove blocking sequences, and installed a deliberate operating cadence \u2014 daily flow, weekly architecture, monthly performance." }, { label: "OUTCOME", accent: "#14B89A", title: "Delivered as a clean line.", body: "The workstream landed on the date originally committed, with no senior escalations and minimal downstream impact. Delivery moved as one continuous line \u2014 and the change in operating rhythm held after the engagement closed." }]; return (
{/* Top: eyebrow + headline + lift */}
ENGAGEMENT IN FOCUS

A critical cloud migration. Delivered as a clean line.

An enterprise cloud migration where a critical workstream was at risk. The constraint was structural — not capability.

{/* Before / After visual */}
BEFORE · REACTIVE AFTER · ON A CLEAN LINE
{/* horizontal baseline grid */} {[60, 110, 160].map((y, i) => )} {/* baseline axis */} {/* Left half: chaotic line */} {/* Escalation markers (red X) along chaotic line */} {[ { cx: 110, cy: 175 }, { cx: 195, cy: 185 }, { cx: 285, cy: 170 }, { cx: 370, cy: 180 }]. map((p, i) => )} {/* Middle: PSL Engagement marker */} PSL ENGAGEMENT {/* Right half: clean ascending line */} {/* Endpoint marker */} {/* X axis label */} DELIVERY OVER TIME ON-DATE DELIVERY {/* Legend */}
Reactive delivery, escalation-driven
Senior escalations
Structured delivery after engagement
{/* Stats row */}
{stats.map((s, i) =>
{s.n}
{s.l}
{s.d}
)}
{/* Narrative: 3 columns */}
{rows.map((row, i) =>
{row.label}

{row.title}

{row.body}

)}
); }; /* ===================================================================== INSIGHTS v3 \u2014 single featured article card. Preserved. v4 below. ===================================================================== */ const HRefined_Insights_v3 = () =>
FROM THE LAB

Recent thinking on performance under pressure.

Visit the Insights Hub
{/* Featured article — big editorial card */} {e.currentTarget.style.borderColor = '#1F4DD8';e.currentTarget.style.boxShadow = '0 12px 32px rgba(31,77,216,0.10)';}} onMouseLeave={(e) => {e.currentTarget.style.borderColor = '#D9DFE9';e.currentTarget.style.boxShadow = 'none';}}>
SUSTAINABLE CAPACITY LATEST

Recovery Is Inevitable.
The Only Question Is Whether It Is Planned.

How sustained-pressure delivery environments turn refused recovery into unplanned absence — and what to do about it.

PUBLISHED
5th May 2026
READ TIME
9 minutes
Read article
More pieces are in development. The library expands as the methodology research progresses.
; /* ===================================================================== BREAKS DOWN v5 — preserved for revert. New v6 below, ring-aligned colors. ===================================================================== */ const HRefined_BreaksDown_v5 = () => { const items = [ { n: "01", label: "IDENTITY", sub: "Where standards live", t: "Standards quietly default under pressure.", d: "When the team's behavioural anchor isn't deliberately designed, performance habits drift downward under load. Quality bars slip a percentage at a time \u2014 until \"how we do things\" has quietly become something else.", accent: "#F472B6", motif: }, { n: "02", label: "EXECUTION", sub: "Where intent becomes action", t: "Effort multiplies. Output does not.", d: "When the underlying flow isn't designed, priorities drift, dependencies pile up, and shipped output thins out \u2014 even as everyone works harder. Heroic compensation hides the structural fault.", accent: "#FBBF24", motif: }, { n: "03", label: "CAPACITY", sub: "Where the reserves live", t: "Intensity becomes the system. Then it isn't.", d: "When recovery and load aren't structured, senior people absorb what the system cannot. It works for a quarter, maybe two. Then engagement thins, decision quality drops, and capacity collapses without a visible failure point.", accent: "#EF4444", motif: }]; return (

Where performance breaks down.

Most approaches to performance were designed for stable conditions. When pressure does not let up, effort alone stops being enough. Performance problems are not people problems — they are architecture problems, and they appear in three specific places.

{items.map((it) =>
{/* Short accent rule top — matches Engagement narrative */}
{/* Header: label/sub left, motif right */}
{it.n} · {it.label}
{it.sub}
{it.motif}

{it.t}

{it.d}

)}
); }; /* ===================================================================== BREAKS DOWN v6 — ring-aligned colours (violet/teal-blue/electric blue) matching the Performance System rings below. Subtle accent glow at top of each card adds depth without overpowering. "Maps to → X Ring" line makes the visual thread explicit. To revert: render in root. ===================================================================== */ const HRefined_BreaksDown = () => { const items = [ { n: "01", label: "IDENTITY", sub: "Where standards live", t: <>Standards quietly default under pressure., d: "When the team's behavioural anchor isn't deliberately designed, performance habits drift downward under load. Quality bars slip a percentage at a time \u2014 until \"how we do things\" has quietly become something else.", ring: "Inner ring", accent: "#A78BFA", glow: "rgba(167,139,250,0.20)", motif: }, { n: "02", label: "EXECUTION", sub: "Where intent becomes action", t: <>Effort multiplies. Output does not., d: "When the underlying flow isn't designed, priorities drift, dependencies pile up, and shipped output thins out \u2014 even as everyone works harder. Heroic compensation hides the structural fault.", ring: "Middle ring", accent: "#2EE0B0", glow: "rgba(46,224,176,0.20)", motif: }, { n: "03", label: "CAPACITY", sub: "Where the reserves live", t: <>Intensity becomes the system. Then it isn’t., d: "When recovery and load aren't structured, senior people absorb what the system cannot. It works for a quarter, maybe two. Then engagement thins, decision quality drops, and capacity collapses without a visible failure point.", ring: "Outer ring", accent: "#6366F1", glow: "rgba(99,102,241,0.24)", motif: }]; return (

Where performance breaks down.

Most approaches to performance were designed for stable conditions. When pressure does not let up, effort alone stops being enough. Performance problems are not people problems — they are architecture problems, and they appear in three specific places.

{items.map((it) =>
{/* Short accent rule top — matches Engagement narrative */}
{/* Header: ring badge + label/sub left, motif right */}
{/* Ring indicator badge — moved up to title area */}
RING {it.n} · {it.label}
{it.sub}
{it.motif}

{it.t}

{it.d}

)}
); }; /* ===================================================================== PRINCIPLES v2 \u2014 cards with header imagery (sport / research / field). Preserved v1 above. To revert: render in root. ===================================================================== */ const HRefined_Principles = () => { const items = [ { tag: "FROM SPORT", t: "Elite Performance Environments", c: "RING-TESTED METHOD", img: "assets/photos/sport-bw.jpg", imgAlt: "Athletes mid-action \u2014 composite of training and competition", theme: "violet", accent: "#7C3AED", b: "In boxing, a fighter's performance in the ring is the direct product of how the fight camp was designed \u2014 preparation cycles, recovery discipline, identity stability, composure under consequence. The same architecture applies to senior delivery work. PSL adapts the principles that produce repeatable performance in elite sport for environments where the contest is corporate and the pressure is sustained." }, { tag: "FROM RESEARCH", t: "High-Performing Teams Research", c: "MCKINSEY \u00b7 PROJECT ARISTOTLE", img: "assets/photos/research-analyst.jpg", imgAlt: "Analyst reflected in screen \u2014 data over the eye", theme: "mint", accent: "#0F766E", b: "McKinsey's work on organisational health and Google's Project Aristotle on team effectiveness independently point to the same conclusion: sustained team performance is a property of the operating system, not of individual talent." }, { tag: "FROM THE FIELD", t: "Real Delivery Experience", c: "10+ YEARS", img: "assets/photos/field-engineer.jpg", imgAlt: "Engineer at a multi-screen delivery workstation", theme: "blue", accent: "#1F4DD8", b: "Grounded in over a decade of leading complex delivery programmes across financial services, global retail, and enterprise technology. Whether the team runs Agile, waterfall, or hybrid, the pattern of where performance breaks down is consistent \u2014 and structurally addressable." }]; return (
BUILT ON PROVEN PERFORMANCE PRINCIPLES

Drawn from sport. Validated by research. Proven in delivery.

The PSL Performance System is not a theoretical model. It draws on three sources that have each been pressure-tested independently — and converge on the same structural conclusions about how performance is produced under sustained load.

{items.map((p) =>
{/* Image header */}
{p.imgAlt}
{p.tag}
{/* Body */}

{p.t}

{p.b}

{p.c}
)}
); }; /* ===================================================================== INSIGHTS v4 \u2014 featured card with editorial hero image To revert: render (or earlier) in root. ===================================================================== */ const HRefined_Insights = () =>
FROM THE LAB

Recent thinking on performance under pressure.

Visit the Insights Hub
{/* Featured article \u2014 hero image left, editorial content right */} {e.currentTarget.style.borderColor = 'rgba(31,77,216,0.5)';e.currentTarget.style.boxShadow = '0 14px 40px rgba(13,0,66,0.08)';}} onMouseLeave={(e) => {e.currentTarget.style.borderColor = 'rgba(13,0,66,0.10)';e.currentTarget.style.boxShadow = 'none';}}> {/* Image */}
; /* ===================================================================== CASE STUDY v5 \u2014 same structure as v4, cool brand palette. Sits in the page's white/cool gradient family. Accent colors use brand pink/blue/teal. To revert: render in root. ===================================================================== */ const HRefined_CaseStudy = () => { const stats = [ { n: "On time", l: "Committed delivery date", d: "Landed on the date originally committed." }, { n: "Full scope", l: "Nothing cut to meet the date", d: "Original outcomes delivered end to end." }, { n: "0", l: "P1 escalations", d: "Resolved structurally, not reactively." }, { n: "0", l: "Rollbacks", d: "Cutovers proceeded without reverting changes." }]; const rows = [ { label: "CHALLENGE", accent: "#F472B6", title: "A workstream slipping under pressure.", body: "A critical workstream slipping inside an enterprise cloud migration. The people were capable; the dependency map was tangled, ownership was unclear, and the operating rhythm was reactive." }, { label: "RESPONSE", accent: "#1F4DD8", title: "Rebuilt the structure underneath.", body: "Restructured the delivery teams. Redesigned the dependency map. Installed a deliberate operating cadence \u2014 daily flow, weekly architecture, monthly performance." }, { label: "OUTCOME", accent: "#14B89A", title: "Delivered as a clean line.", body: "Landed on the date originally committed. No senior escalations. Minimal downstream impact. The change in operating rhythm held after the engagement closed." }]; return (
{/* Top: eyebrow + headline + lift */}
CASE STUDY IN FOCUS

A critical cloud migration. Delivered as a clean line.

An enterprise cloud migration where a critical workstream was at risk. The constraint was structural — not capability.

{/* Before / After visual */}
BEFORE · REACTIVE AFTER · ON A CLEAN LINE
{[60, 110, 160].map((y, i) => )} {/* Left half: chaotic line */} {[ { cx: 110, cy: 175 }, { cx: 195, cy: 185 }, { cx: 285, cy: 170 }, { cx: 370, cy: 180 }]. map((p, i) => )} {/* Middle: PSL Engagement marker */} PSL ENGAGEMENT {/* Right half: clean ascending line */} DELIVERY OVER TIME ON-DATE DELIVERY {/* Legend */}
Reactive delivery, escalation-driven
Structured delivery after engagement
{/* Stats row */}
{stats.map((s, i) =>
{s.n}
{s.l}
{s.d}
)}
{/* Client quote — punctuates proof moment between stats and narrative */}
“
“PSL didn’t just resolve the workstream — they rebuilt the operating rhythm underneath it. The change held after they left, which is the part most consultancies don’t deliver.”
Programme Manager, FTSE-listed retailer
{/* Narrative: 3 columns */}
{rows.map((row, i) =>
{row.label}

{row.title}

{row.body}

)}
); }; /* ===================================================================== ROOT ===================================================================== */ const HomeRefined = () =>
; Object.assign(window, { HomeRefined, // Expose internal sections so HomeMinimal (separate Babel scope) can reuse them. HRefined_Hero, HRefined_Stats, HRefined_BreaksDown, HRefined_System, HRefined_Principles, HRefined_Routing, HRefined_CaseStudy, HRefined_Insights, HRefined_FAQ });