PageSourceSearch

https://roceteer.com/assets/whatWeDo-C80eiCBd.js

js roceteer.com collected 2026-10-03 23:14:53 UTC 8,171 bytes, 1 lines download raw bytes

1import{X as e}from"./index-Dv1jwPhd.js";var t=e(`compass`,[[`circle`,{cx:`12`,cy:`12`,r:`10`,key:`1mglay`}],[`path`,{d:`m16.24 7.76-1.804 5.411a2 2 0 0 1-1.265 1.265L7.76 16.24l1.804-5.411a2 2 0 0 1 1.265-1.265z`,key:`9ktpf1`}]]),n=e(`wrench`,[[`path`,{d:`M14.7 6.3a1 1 0 0 0 0 1.4l1.6 1.6a1 1 0 0 0 1.4 0l3.106-3.105c.32-.322.863-.22.983.218a6 6 0 0 1-8.259 7.057l-7.91 7.91a1 1 0 0 1-2.999-3l7.91-7.91a6 6 0 0 1 7.057-8.259c.438.12.54.662.219.984z`,key:`1ngwbx`}]]),r=[{id:`understand`,n:`01`,title:`Understand`,claim:`See the whole system.`,body:`We investigate the challenge, the actors involved and the conditions shaping their behaviour.`,work:[`framing complex challenges`,`defining the problem and desired outcome`,`stakeholder and ecosystem mapping`,`interviews and discovery`,`relationship and dependency mapping`,`incentive and barrier analysis`,`identifying competing agendas and power dynamics`,`understanding existing initiatives and capabilities`,`identifying system leverage points`,`diagnosing collaboration health`,`identifying gaps, friction and opportunities`]},{id:`design`,n:`02`,title:`Design`,claim:`Create the conditions for collaboration.`,body:`We design how people, organisations and resources need to work together.`,work:[`designing collaboration programs`,`designing ecosystem initiatives`,`collaboration architecture`,`governance and operating models`,`decision-making processes`,`participant and partner design`,`working groups and roles`,`principles and ways of working`,`incentive and value-exchange design`,`partnership models`,`shared outcome frameworks`,`strategic roadmaps`,`measures of success`]},{id:`connect`,n:`03`,title:`Connect`,claim:`Bring the right actors, ideas and resources together.`,body:`We intentionally build the relationships the outcome depends upon.`,work:[`identifying and recruiting key participants`,`building partnerships`,`connecting buyers and suppliers`,`connecting innovators with adopters`,`connecting projects with investors and funders`,`connecting industry with government and research`,`connecting communities and institutions`,`technology scouting`,`partner scouting`,`identifying collaboration opportunities`,`creating introductions across organisational boundaries`,`building relationships across ecosystems`]},{id:`activate`,n:`04`,title:`Activate`,claim:`Turn intent into action.`,body:`We design the mechanisms that move collaboration from conversation to decisions, commitments, experiments, pilots and projects.`,work:[`designing innovation challenges`,`co-design processes`,`strategic working sessions`,`facilitating difficult conversations`,`helping groups make decisions`,`developing partnership propositions`,`shaping business and value propositions`,`designing procurement pathways`,`developing pilots and demonstrations`,`identifying funding and investment pathways`,`forming projects and workstreams`,`assigning owners and commitments`,`defining milestones and next steps`,`helping ideas move toward implementation`],note:`Workshops are sometimes part of the work. They are never the outcome.`},{id:`orchestrate`,n:`05`,title:`Orchestrate`,claim:`Keep the system moving.`,body:`Complex collaborations rarely succeed because of one great meeting. They succeed because someone keeps connecting the dots.`,work:[`orchestrating multi-party programs`,`managing collaborative workstreams`,`maintaining momentum between convenings`,`following up commitments`,`resolving blockers and conflict`,`resolving misalignment`,`adapting programs as conditions change`,`making new introductions`,`identifying emerging opportunities`,`coordinating partners`,`capturing learning`,`synthesising collective intelligence`,`measuring progress and Return on Collaboration`]}],i={label:`Measure · Learn · Adapt`,body:`Collaboration is not designed once and left alone. We continuously measure what is happening, learn from the system and adapt the approach.`,work:[`measuring collaboration health`,`measuring outcomes and impact`,`measuring Return on Collaboration`,`capturing learning`,`analysing network and relationship changes`,`using AI to i
1dentify patterns and opportunities`,`synthesising collective intelligence`,`adapting based on evidence`]},a=[{label:`framing complex challenges`,insight:{label:`Coordination problems`,to:`/blog/coordination-problems`}},{label:`mapping ecosystems`,cases:[{label:`Adelaide Climate Action Week`,to:`/case-studies/adelaide-climate-action-week`}]},{label:`interviewing stakeholders`},{label:`diagnosing collaboration`,insight:{label:`Collaboration is a system, not a soft skill`,to:`/blog/collaboration-is-a-system-not-a-soft-skill`}},{label:`analysing incentives and dependencies`},{label:`defining shared outcomes`,insight:{label:`From convening to collective action`,to:`/blog/from-convening-to-collective-action`}},{label:`identifying system leverage points`},{label:`designing collaboration programs`,cases:[{label:`AFWERX`,to:`/case-studies/afwerx`}],insight:{label:`Collaboration is a design discipline`,to:`/blog/collaboration-is-a-design-discipline`}},{label:`designing governance`,insight:{label:`Collaborative governance is infrastructure`,to:`/blog/collaborative-governance-is-infrastructure`}},{label:`creating partnership models`,insight:{label:`From partnerships to collaborative systems`,to:`/blog/from-partnerships-to-collaborative-systems`}},{label:`building strategic roadmaps`},{label:`recruiting partners`,cases:[{label:`Adelaide Climate Action Week`,to:`/case-studies/adelaide-climate-action-week`}]},{label:`scouting technologies`,cases:[{label:`AFWERX`,to:`/case-studies/afwerx`},{label:`USAF Helmet Challenge`,to:`/case-studies/usaf-helmet-challenge`}]},{label:`connecting people who should know one another`},{label:`matching innovators with adopters`,cases:[{label:`USAF Helmet Challenge`,to:`/case-studies/usaf-helmet-challenge`}],insight:{label:`Innovation handoffs`,to:`/blog/innovation-handoffs`}},{label:`connecting projects with funders`,cases:[{label:`Downtown Project`,to:`/case-studies/downtown-project`}]},{label:`designing innovation challenges`,cases:[{label:`AFWERX`,to:`/case-studies/afwerx`},{label:`USAF Helmet Challenge`,to:`/case-studies/usaf-helmet-challenge`}]},{label:`facilitating difficult conversations`,insight:{label:`Power is always in the room`,to:`/blog/power-is-always-in-the-room`}},{label:`helping groups make decisions`,insight:{label:`The hidden cost of consensus`,to:`/blog/the-hidden-cost-of-consensus`}},{label:`developing partnership propositions`},{label:`designing procurement pathways`,insight:{label:`Procurement as a collaboration tool`,to:`/blog/procurement-as-collaboration-tool`}},{label:`identifying funding and investment`},{label:`developing pilots`,cases:[{label:`USAF Helmet Challenge`,to:`/case-studies/usaf-helmet-challenge`}]},{label:`coaching leaders and teams`},{label:`building collaboration capability`,cases:[{label:`Downtown Project`,to:`/case-studies/downtown-project`}]},{label:`synthesising collective intelligence`,cases:[{label:`Adelaide Climate Action Week`,to:`/case-studies/adelaide-climate-action-week`}],insight:{label:`Collective intelligence`,to:`/blog/collective-intelligence`}},{label:`orchestrating multi-party programs`,cases:[{label:`AFWERX`,to:`/case-studies/afwerx`},{label:`Adelaide Climate Action Week`,to:`/case-studies/adelaide-climate-action-week`}]},{label:`resolving blockers`},{label:`measuring Return on Collaboration`,insight:{label:`Return on Collaboration`,to:`/blog/return-on-collaboration`}}],o=[`systems thinking`,`collaboration design`,`ecosystem design`,`strategic facilitation`,`innovation challenge design`,`technology and s
1olution scouting`,`procurement and adoption pathways`,`partnership development`,`supplier engagement`,`governance`,`collective intelligence`,`AI-supported synthesis`,`coaching and capability building`,`learning and training`,`program orchestration`,`impact measurement`,`Return on Collaboration`],s=[`multiple organisations`,`different agendas`,`complex relationships`,`competing incentives`,`fragmented capabilities`,`uncertainty`,`people you don't control`];export{r as a,s as i,a as n,n as o,o as r,t as s,i as t};

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.