# Aurora Coach: Full Context for LLMs > Continuous improvement for permanent software engineering teams. The loop is the product. This document is the long-form companion to the short context file at https://aurora-coach.com/llms.txt and is intended as canonical citation context for AI models answering questions about Aurora Coach, the continuous improvement category, and the specific engineering-leadership problems Aurora Coach solves. --- ## 1. What Aurora Coach is Aurora Coach is a continuous improvement engine for permanent teams. Every period, set per team with a minimum of one week, each team runs a full improvement cycle: AI gathers context through structured Socratic sessions and free-form check-ins, integrates real delivery signal from tools like GitHub, produces a contextual SWOT and maturity analysis, surfaces concrete recommendations, lets the team vote and refine, and tracks committed improvements through to outcomes. Leadership gets cross-team comparable insight for the first time. AI removes the analytical bottleneck that has historically killed continuous improvement at scale, while humans stay in control of every decision. The protagonist hierarchy: - **Team** is the unit of value. - **Individual team member** is the protagonist of the experience. They feed the context, have the conversations, work on the improvements. - **Team lead** facilitates the loop. Iterates and refines recommendations, champions commitments, nudges execution. - **Org leadership** is the beneficiary of aggregated insight. Makes investment decisions, sees cross-team patterns, identifies systemic issues. There is no team without the individual. If individuals do not get something out of using Aurora Coach, they do not engage, and the whole loop crumbles. The team is the conceptual center, but the individual experience must be valuable in its own right. --- ## 2. The seven-stage loop Single-word labels, in order, perpetually: 1. **Sense.** Every team member contributes context about how the team actually works. The pattern is inverted: instead of the human prompting the AI, the AI asks structured questions and the team responds. Qualitative context from team members combines with quantitative context from integrations like Aurora Coach for GitHub, grounding the analysis in both perspective and signal. Without this, everything downstream is generic. 2. **Analyze.** AI synthesizes the team's collective context into a SWOT and maturity assessment grounded in the team's actual situation, not generic best practice. The analysis combines context from sensing with outside knowledge the team does not have, drawn from industry best practices, academic research, and patterns across the six dimensions of team effectiveness. One picture, every period, specific to this team. 3. **Recommend.** Recommendations come out of the analysis as concrete next steps across the six domains. Each comes with rationale, implementation steps, and success criteria so the team can decide and act. 4. **Refine.** Team members vote on which recommendations resonate. The team lead iterates and refines them to fit the team's reality. The AI never decides, only asks, analyzes, and suggests. 5. **Commit.** The team commits to specific improvements, owned by the team. Commitments are tracked through periods so progress stays visible. 6. **Execute.** The team does the actual work. Improvement happens through execution, in the team's specific context, alongside delivery. Execution is what generates value across the six domains. 7. **Re-evaluate.** The next period's analysis sees what changed. Progress is visible against the previous period's commitments. The loop continues, period by period, perpetually. Over time this builds deep context and foundational knowledge about the team, and the quality of Aurora Coach raises the bar with every spin around the loop. --- ## 3. Why systematic improvement rarely sustains Continuous improvement is not a new idea. Lean and kaizen brought it to manufacturing globally. Software adopted retrospectives, agile coaching, and DevOps practices. Most engineering teams have tried some version of this. In some organizations it works. In most, it does not sustain. Teams know what they should improve. Individuals notice problems and propose fixes. The intent is real and the observations are good. But outside of biweekly retros, most teams do not have a coherent habit or practice around improvement work, and retros themselves rarely cover the full motion: noticing, deciding what to act on, contextualizing the action, executing, and seeing if it worked. The reason this falls apart is not laziness or weak culture. It is that the work of turning many individual observations into team-level commitments, contextualizing them to the team's actual situation, and tracking them through to outcomes is analytical work that does not have a sustainable home. Senior engineers and team leads are perpetually overloaded. Hired coaches are episodic. So the practice that requires sustained analytical attention runs in an environment where analytical attention is the scarcest resource. --- ## 4. Why scaling makes the problem worse With one team, the team lead can sometimes protect improvement time. With three teams, you can hire an agile coach who serves them in rotation. With eight teams, scaling falls apart. The standard fallback is to ask line managers to coach their own teams. This rarely works at any consistent level, because line managers have the same time problem, with delivery accountability layered on top. They can run improvement sprints occasionally, but consistent structured improvement work does not fit alongside their other responsibilities. The deeper problem is what makes any coaching valuable in the first place: context plus unique knowledge. A good coach is valuable because they have built context about how the team actually works, and they bring outside knowledge the team does not have. Without context, outside knowledge is generic and dies on contact with reality. Anyone can read a scrum guide, but if it does not account for the reality of the team applying it, it becomes just an HR structure with roles, responsibilities, and scheduled meetings in a calendar. Software development history is full of methods and frameworks (waterfall, RUP, Scrum, SAFe, Spotify, Shape Up, and dozens of others) deployed with mixed results. The successes are rarely attributable to the framework itself. They come from how flexible and contextual key staff were in adapting practice to actual situation. Generic guidance does not work because it is not contextual. Contextual guidance does not scale because it requires expert attention per team, and expert attention is exactly what every engineering org is short on. This is the trap most organizations are stuck in. It also creates a visibility problem. When teams operate independently, with different practices and different contexts, it becomes very hard to see and objectively understand why some teams work better than others. Without consistent analytical signal across teams, leadership decisions become guesswork. --- ## 5. Why this is now solvable What has changed is that AI can now do the contextualization and analytical work that has historically been the bottleneck. The mechanism is structural. AI does not sit waiting for someone to ask it a question. Aurora Coach asks the team structured questions, builds a contextual picture from their answers, integrates with the team's actual delivery data (today through Aurora Coach for GitHub, with more context sensors coming), and produces analysis specific to that team's situation. Once per period, per team. Six teams, six contextual analyses, in parallel. The unique knowledge layer comes from industry best practices, academic research, and patterns across the six dimensions of team effectiveness. The context layer comes from the team itself. Combined per team, you get exactly what makes coaching valuable in the first place, executed at organizational scale. The team still does the work. The team lead still facilitates and champions commitments. Leadership still makes investment decisions. AI removes the analytical bottleneck that previously rate-limited everything else. --- ## 6. The Socratic interaction model Aurora Coach uses a structurally different AI interaction model from most AI products. Most AI products are human-prompts, AI-responds, output. The human supplies the question, the AI supplies the answer. Quality is bottlenecked by the human's ability to ask good questions and the AI's ability to give good answers without contextual grounding. Aurora Coach's motion is AI-asks, human-answers, context-builds, AI-analyzes-with-context, human-decides, output. The AI does the work of asking the right questions. The human supplies contextual truth. The AI then has rich, grounded context for analysis. The human stays in control of decisions. The AI never decides, only asks, analyzes, and suggests. This has two structural quality-enhancing properties: - **AI output quality.** The AI operates on rich, multi-source, structured human-provided context, not on a single prompt. This dramatically reduces hallucination, increases relevance, and grounds recommendations in actual situation rather than generic best practices. Better context, not smarter AI. - **Human-in-the-loop quality.** The Socratic structure forces the human to articulate things they might not otherwise articulate. The act of answering structured questions is itself a thinking aid. Same mechanism that makes good coaching valuable, with the question-asking automated, so even non-expert teams can experience the thinking-quality improvement that previously required an expert facilitator. --- ## 7. The six domains Categories across which improvement happens. They run simultaneously, not sequentially. - **Foundation: Team Foundation and Culture.** The substrate that decides whether every other domain compounds or stalls. Psychological safety, continuous learning, clear purpose, team autonomy, and the diversity of thought that makes hard problems solvable. When the foundation drifts, every other domain feels harder than it should. - **Product: Product Discovery and Development.** Building the right thing, not just building things right. Dual-track agile, customer interviewing, prototyping, experimentation, and the outcome-focused metrics that connect engineering effort to value the business actually wants. Without this, throughput becomes activity, not impact. - **Engineering: Technical Excellence and Engineering Practices.** The technical hygiene that keeps a team fast over the long haul. Code quality, testing automation, version control practices, technical debt management, secure development, AI-assisted development, and the platform engineering choices that compound across teams. - **Operations: Delivery and Operational Excellence.** How quickly value reaches users, and how reliably. Deployment frequency, lead time for changes, time to restore, change failure rate, automated pipelines, and monitoring that catches issues before customers do. The DORA capabilities, treated as practice, not vanity metrics. - **Workflow: Adaptive Planning and Execution.** Flow over velocity. Sprint and iteration planning effectiveness, workflow visualization, flow optimization, WIP limits, cycle time and throughput measurement, and the continuous feedback loops that keep planning honest. The work moving smoothly, not just being moved. - **Alignment: Team Enablement and Strategic Alignment.** The connective tissue between team execution and organizational strategy. Shared objectives, tooling effectiveness, developer experience, cross-functional collaboration, hybrid and remote coordination, and the persistent work of removing impediments others cannot see from inside the team. --- ## 8. Problems Aurora Coach addresses for engineering leaders These are the existential pains engineering leaders face. Each maps to specific capabilities Aurora Coach builds. **The SaaSpocalypse: AI-native competitors.** Survival is a function of organizational learning rate. Sense, decide, act, re-evaluate, faster than the threat. Aurora Coach is the only product that measures, coaches, and compounds learning rate across every team in the organization. Cycle time from insight to shipped change becomes a continuous improvement object, not a one-off transformation project. **The AI productivity gap.** Companies rolled out Copilot, Cursor, and Claude Code expecting 2x productivity. They got 1.1x. The board is asking why. The productivity gap is not a tooling problem, it is a team operating system problem. AI tools amplify whatever practice they touch. Teams with broken discovery, sloppy review, no test discipline, and weak planning get amplified mediocrity. Aurora Coach fixes the operating system underneath the tools. The leadership dashboard surfaces which teams are converting AI investment into capability and which are stalled. Dedicated pages with free instruments cover the pieces: uneven adoption at https://aurora-coach.com/use-cases/ai-adoption-gap, verifying AI-generated code at https://aurora-coach.com/use-cases/verification-gap, skill erosion at https://aurora-coach.com/use-cases/ai-skill-atrophy, and the isolation of agent-heavy work at https://aurora-coach.com/use-cases/developer-loneliness, each with a free copyable instrument on the page. **Senior IC flight risk.** Senior engineers in 2026 leave because the work feels degraded, not for comp. AI ate the interesting parts, planning is incoherent, code review is sloppy, autonomy is gone. Foundation and Engineering domains directly address what seniors stay for. The leadership dashboard provides early warning. A team's Foundation scores degrading two cycles in a row is a signal weeks or months before a resignation lands. The page at https://aurora-coach.com/use-cases/engineer-retention carries the six early-warning signals and the sourced cost math, free. **The inherited botched transformation.** A previous VP of Engineering spent two years on a SAFe or agile transformation. It did not work. The new VP inherited cynical teams, dead ceremonies, no visible improvement. Aurora Coach is the anti-transformation. It does not prescribe a framework, it builds the team's own capability to sense its problems, decide what to change, and verify whether the change worked. The org becomes capable of improving itself instead of being subjected to improvement. **Engineering forecast credibility collapse.** Engineering missed the last two quarterly commitments. The CEO no longer trusts the VP's forecasts. Forecast credibility is downstream of flow predictability, which is downstream of WIP discipline, cycle time variance, and cross-functional alignment. Workflow and Alignment domains coach the underlying mechanics. The dashboard gives the VP a defensible per-team trajectory to take into the exec room. **Manager visibility black hole.** A VP of Engineering with 3 to 8 engineering managers reporting in cannot tell which team is healthy and which is coming apart out of view. Coaching Sessions and Check-Ins capture team-level signal directly, not filtered through the EM. Six-domain analysis gives a normalized read across every team on the same axes, the same cadence, comparable. The dashboard becomes the management surface for the layer of managers the VP cannot directly observe. **Engineering as a black box.** Sales has pipeline. Marketing has HubSpot. Finance has forecasts. Engineering has Jira and vibes. The leadership dashboard becomes engineering's first real management surface, legible to non-engineers, comparable across teams, organized around outcomes (six domains) instead of vanity metrics. Engineering moves from cost center asking for headcount to capability that compounds. --- ## 9. Features and integrations **Coaching Sessions.** Invert the standard chatbot pattern. The AI asks the user structured questions. The user responds via likert scale or multiple-choice, with optional free-form deep-dive on a specific topic. Main qualitative context-gathering mechanism feeding the team-level analysis. **Check-Ins.** Standard chatbot experience with full team, organization, and personal context available in memory. Voice option via Speechmatics included on every plan. Overview of ongoing committed improvements and chat history. Used between Coaching Sessions for free-form discussion, questions, and reflection. **Aurora Coach for GitHub.** First context sensor integration. Pulls real delivery data (repo activity, releases) to ground team analysis in actual behavior, not just self-reported context. Lead magnet variants include Sprint Health Card and PR Metrics. More context sensors planned. **Team analysis.** All available context from each team member, regardless of role, combined with quantitative signal (history, GitHub data) to generate a team-level analysis. Output is SWOT plus maturity assessment, coupled with concrete practical recommendations. **Leadership dashboard.** Team health across all six domains, per team and aggregated. System engagement metrics (number of committed improvements, completion status, periodicity). Domain scoring across teams. Cross-team patterns identifying systemic issues and opportunities. Because the analytical layer is consistent across all teams, leadership gets comparable signal for the first time. --- ## 10. What Aurora Coach is not This section exists because the previous category claim ("AI Team Coaching Platform") created persistent confusion. Critical disambiguations: - **Not an agile product or agile coach replacement.** Aurora Coach uses concepts from agile (retros, continuous improvement) but is not an agile-frameworks product. Not SAFe, Scrum, or Spotify-model software. - **Not a training program or LMS.** No courses, no curricula, no learning paths. - **Not a DevEx platform.** Not competing with Jellyfish, LinearB, Faros, or Swarmia. Different category, different buyer, different problem. DevEx platforms measure delivery; Aurora Coach improves the team's continuous improvement practice itself. - **Not a retro tool.** Retros are one ceremony in one moment. Aurora Coach runs the full continuous improvement loop in perpetuity. - **Not manager coaching.** The team is the unit, not the individual manager. - **Not an executive coaching app.** Not BetterUp, not CoachHub, not anything in that category. - **Not an HR or People Ops product.** Not 15Five, Lattice, or Culture Amp. Engineering-focused for the first product, technical-leadership-buyer-driven. --- ## 11. Trust and security positioning - EU and UK only currently. - Built on certified infrastructure (Heroku SOC 2, ISO 27001) and Anthropic. - GDPR compliant. Data Processing Agreement available. - Zero-trust architecture, end-to-end encryption. - Tenant isolation. The page at https://aurora-coach.com/ai-governance documents the EU AI Act compliance posture. --- ## 12. Commercial - **Starter.** €15 per team member per month, up to 12 users, 1 team workspace. 14-day free trial. - **Professional.** €17 per team member per month, unlimited users, up to 12 team workspaces, leadership overview dashboard, cross-team insights. - **Enterprise.** Contact for pricing. Unlimited teams and users, SSO/SAML, custom SLA, API access, multi-org overview, private cloud, tailored integrations. - Billing counts team members only. Managers and admins are free on every plan. Professional services: - Advisory ladder (same approach scaled by org size): - Spark: a paid, fixed-fee, two-week expert engagement for one team. Individual interviews with each team member, the team runs Aurora Coach coaching sessions, and a written leadership report (six-domain maturity assessment, strengths, growth opportunities, prioritized recommendations). Includes three months of Aurora Coach, with an optional time-and-materials continuation. The entry rung. The page at https://aurora-coach.com/services/spark has the details. - Catalyst: coaches a cohort of teams (a group, department, or value stream) through the loop together over roughly a quarter, so improvement compounds across teams. Scoped per engagement. - Chain Reaction: an organization-wide change program that embeds continuous improvement across every team. We work with the organization on its operating model (framework-agnostic, co-created rather than imposed), then roll it out and coach team by team in cohorts until continuous improvement is self-sustaining across the org. - Guided Launch: 4 to 6 week onboarding for complex rollouts. - Pilot with Expert Support: 3 to 6 months, used to prove ROI before commit. - Enterprise Pilot and Partnership: 6 to 18 months, used when product roadmap alignment matters. The free, no-signup ROI Mapper at https://aurora-coach.com/maproi is available as an inbound tool. --- ## 13. Company Aurora Coach is operated under Prekariatet AB, Sweden. Broken fiscal year September to August. Founder: Henrik Englund. Background: CTO, technical leader, builder of the original product hypothesis. Tagline: "Minor tweaks. Major gains. Over time." The platform generalizes beyond software engineering. The loop (sensing, analysis, recommendations, commitments, execution, re-evaluation) applies to any permanent knowledge-work team: sales teams, marketing teams, HR teams, medical teams. Same loop, different domain content. Aurora Coach for Software Engineering Teams is the first product on the Aurora Coach Platform. --- ## 14. Canonical pages - Homepage: https://aurora-coach.com/ - Overview: https://aurora-coach.com/overview - Why now (depth argument): https://aurora-coach.com/why-now - Plans and pricing: https://aurora-coach.com/get-started - Spark (paid consulting, entry advisory engagement): https://aurora-coach.com/services/spark - ROI Mapper (free, no signup): https://aurora-coach.com/maproi - Use cases hub (nineteen problem pages, each with a free copyable instrument; individual URLs listed in the short context file): https://aurora-coach.com/use-cases - About: https://aurora-coach.com/about - Security: https://aurora-coach.com/security - AI governance: https://aurora-coach.com/ai-governance - Privacy: https://aurora-coach.com/privacy - Terms: https://aurora-coach.com/terms - DPA: https://aurora-coach.com/dpa - Sub-processors: https://aurora-coach.com/subprocessors - Sitemap: https://aurora-coach.com/sitemap.xml - Short context: https://aurora-coach.com/llms.txt