Brand: Artifact vs Operating System
Compare two mental models for brand: a static artifact (logos, guidelines, centralized control) and a living operating system (values, APIs, support, trust). See which choices fit your engineering team.
Loading…
Topic
Onboarding
31 posts about Onboarding. Every summary links to the original.
- 31 posts
- 11 companies
- 1 explainer
See the idea
Onboarding explainers
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
Posts
Harnessing user research with Intercom - The Intercom Blog
TrackDuck, a visual feedback tool for developers, used Intercom to collect user feedback and track behavior, bridging the gap between developer knowledge and user understanding. They simplified a ten-step registration form to just four steps with three entry fields, resulting in a 120% increase in customers who completed registration and started using the system. After discovering through Intercom that some new users never returned after adding their first project, they implemented a seven-step onboarding tour immediately after registration and used auto-messages to track where users dropped off. To satisfy commercial client requests for mobile access without the cost of native apps, they made the control panel adaptive using Media Queries, ngTouch, and matchmedia-ng with a vertical block design. They also added recognizable icons to inline editing fields after users failed to understand that static-looking text was editable, and removed seldom-used features to reduce clutter and focus on valuable functionality.
How We Spread Engineering Knowledge & Culture Across Intercom
Large engineering organizations often face siloed knowledge and culture as teams focus on their own domains. Intercom addresses this with engineering tours, where engineers temporarily transfer to another team to work on a specific project, such as building a scalable solution for database performance issues. New engineers go on tour within their first few months, and all engineers are encouraged to tour at least once a year. Tours are designed with a mentor and can be feature-oriented, shipping a new product or tool with a demo at the weekly Show and Tell, or tech-debt oriented, fixing bugs or performance issues. Beyond code, tours build relationships and spread culture across offices in Dublin, London, and San Francisco, and the concept has expanded to other departments like Customer Support and Marketing; engineers bring back learnings to their home teams.
Ways to think about customer onboarding - The Intercom Blog
Customer onboarding is critical, yet most apps lose half their new users by the second day because it fails to deliver real value. Instead of focusing on feature adoption like creating a to-do list, onboarding should help users achieve their ultimate goal, such as delivering a project on time, turning them into superheroes. The Jobs-to-be-Done framework reveals the motivations driving sign-ups, enabling segmentation and tailored onboarding flows for groups with similar needs. The four forces model adds context by showing push and pull factors when users switch, maximizing forces for change like long email trails and minimizing resistance like switching anxiety. Finally, behavior-based messaging should be scheduled by time with a priority list rather than predefined sequences, avoiding the complexity of N-dimensional decision trees, as implemented in Intercom’s Smart Campaigns.
Effective messages have real goals - The Intercom Blog
Defining a clear goal before sending a customer message is essential for effectiveness and guides message structure. Real goals should focus on eliciting user behavior change such as more frequent product usage, updating billing details, or trying a new feature, not on intermediate metrics like open or click-through rates. Intercom’s Message Goals feature lets you see message impact and measure success against your objective. Onboarding messages should ask users their own goals, new feature messages should explain user benefits to increase adoption or usage frequency, and announcements must ensure recipients understand implications and any required action. Newsletters can stay top of mind, reward paying customer loyalty, or re-engage lapsed users, while surveys should gather quality data to drive business decisions rather than maximizing quantity.
A new getting started experience for ClickHouse Managed Postgres
ClickHouse Managed Postgres introduces a four-step onboarding experience designed to move users from provisioning a service to working with operational data and ClickHouse analytics. Existing onboarding placed new users on an empty Overview page, while the documentation quickstart required users to track progress outside the product. The new flow guides users through creating a service, migrating or ingesting data, running a query in the SQL Console, and configuring Postgres CDC to ClickHouse. Data can arrive through a managed Postgres-to-Postgres ClickPipe, a language client, a sample dataset, or a table created from scratch; pg_clickhouse provides a PostgreSQL query layer over ClickHouse foreign tables. The article reports less than a minute of replication lag and benchmarks showing five aggregations falling from 555 ms to 164 ms and a JOIN with aggregations from 1,246 ms to 170 ms on one million-row data set.
Enterprise-managed auth for the Supabase MCP server
Supabase has generally released enterprise-managed authentication for its MCP server on Supabase Team and Enterprise plans, built with Anthropic and Okta. The change moves authorization for using Supabase in Claude to the organization's identity provider: an administrator authorizes the connector once, while employees receive access according to their existing Supabase projects and permissions. Each query and management action runs with the individual employee's current role, so developers and read-only members do not receive more access than they have in Supabase directly. Okta groups can restrict access, and onboarding, offboarding, and access reviews can be handled through existing identity-provider workflows rather than individual OAuth approvals; availability requires Okta SSO plus a Claude Team or Enterprise plan, with SCIM provisioning listed as a future roadmap item.
Red Hat Ansible development workspaces for governed automation content creation
Ansible development workspaces in Red Hat Ansible Automation Platform leverage Red Hat OpenShift Dev Spaces to solve environment drift and lengthy developer onboarding. Instead of configuring local environments, developers access cloud-hosted VS Code instances via a web browser using declarative devfile.yaml configurations. The platform enforces immutability with a read-only /var directory at runtime, preventing arbitrary package installations that cause configuration drift. To address differing domain requirements across teams without creating bloated monolithic images, the solution implements a four-tiered image strategy based on OpenShift BuildConfigs and ImageStreams. When base container images receive security patches, the dependent image layers automatically rebuild throughout the entire chain.
Enterprise Readiness Is Not What You Support. It Is What Your Customers Can Own
Workplace operations platform SafetyCulture previously relied on a multi-team, manual onboarding process for enterprise single sign-on setups across diverse identity providers, which created operational overhead and accounted for approximately 30 percent of engineering support tickets. To resolve these scaling bottlenecks, the engineering team integrated Auth0's Self-Service Enterprise Configuration, implementing a step-by-step wizard for OpenID Connect and custom SAML setups. The resulting workflow allows customer administrators to configure identity settings, test logins before committing, and manually toggle production activation. Moving from proof-of-concept to general availability took two months, achieving a 50 percent unassisted completion rate. Four months post-launch, SafetyCulture recorded a 60 percent reduction in SSO setup-related customer support tickets.
From Day 1 to Production: Building Lyft’s Analytics & Rides Intelligence Assistant as Onboarding…
Lyft developed Aria, an AI-powered assistant allowing approved employees to query ride analytics via natural language through a backend with LangGraph orchestration and SQL generation. However, Aria's user interface was limited to a Streamlit prototype that lacked standard service framework integration, Lyft authentication, and multi-user scalability. To resolve these limitations, a new engineer built a production-grade web client from scratch using Lyft's internal Node.js framework and Next.js as a three-week onboarding assignment. The implementation involved configuring Envoy routing, resolving authentication plugin incompatibilities, debugging service connectivity with Grafana, and managing interface state with an XState state machine. Aria was successfully hardened and launched into production, expanding natural language analytics access across the company.
Her Tech Circle rebuilt a community from scratch using Notion
After Girls in Tech abruptly ended its global operations, Renece Brewster and Karen Katz had one week to decide how to preserve an Australian community of 18,000 members. They launched Her Tech Circle (HTC), retaining the community’s core values while focusing on helping women in Australia and New Zealand thrive, lead, and contribute in tech. To rebuild quickly, HTC made Notion its digital headquarters, first piloting it with the social media team before rolling it out across the organization. The workspace combines a public-facing volunteer portal, a shared marketing database, and a directory that doubles as an org chart, linking roles, team leads, and peer support. HTC’s experience argues for testing tools early, making knowledge discoverable, and building scalable systems that let volunteers contribute independently rather than concentrating operational knowledge with founders.
Stripe for marketplaces: Mapping commercial relationships in code
The post presents a guide to mapping marketplace relationships among buyers, sellers, and the platform in Stripe Connect, focusing on payment processing, seller onboarding, payouts, fees, refunds, and disputes. It uses Greens & Dairy Mart, a fictitious farm marketplace, to show how an unlicensed marketplace can manage payments with Stripe while meeting applicable regulatory requirements. Using the Account API, connected accounts, controller settings, KYC links, capabilities, Payment Intents, transfers, and webhooks, the implementation encodes responsibilities and money movements. Greens & Dairy Mart charges customers after farmers confirm dispatch, pays farmers after delivery confirmation, and retains 15% of the final price. The guide also shows refund and transfer reversal flows, including recovering disputed amounts from a seller’s balance, and concludes that Connect APIs can automate complex marketplace contracts and financial interactions.
Growth Intern to Procurement New Grad
A 2023 summer internship on Ramp’s growth engineering team changed the author’s view of software engineering and led to a return as a new graduate engineer. The team accelerated outbound sales through fast experiments, metric ownership, and decisions about whether promising tactics deserved scalable systems, rather than following the thorough specification process typical of regular projects. His work included reducing third-party data-enrichment costs, building AI-driven outbound-sales tools, adding observability and service monitors, and conducting competitive intelligence projects. He returned to join the new procurement product line, where he helped match card transactions to purchase orders and led additional projects. The post also recommends rapidly building system context through code review and on-call shadowing, while full-time engineers should weigh velocity against maintainability and take initiative on less-defined problems.
Puzzle’s Notion Playbook: Eight Startup Hacks to Save 8+ Hours Weekly
Puzzle presents Notion as the central operating system for its startup, using it as a single source of truth for company knowledge, workflows, and collaboration. The playbook describes eight practices, including integrating tools and legacy content, standardizing recruiting and onboarding, supporting asynchronous communication, organizing teamspaces, building documentation habits, applying AI, and connecting task management to strategic priorities. Its implementation relies on templates, checklists, permissions, comments, @mentions, automations, relations, rollups, database views, formulas, and verification controls. For a team of 50+ employees, Notion AI reportedly saves about ten minutes per query; five daily queries per person are calculated as more than twenty-one hours saved weekly across the company. The conclusion recommends starting with one area, such as meeting documentation or onboarding guides, before expanding.
Creating reusable developer environments with Stripe Sandboxes
Setting up development machines with the correct tools, permissions, and dependencies can take weeks for new engineers, so the setup combines Stripe Sandboxes with development containers. Stripe Sandboxes provide isolated accounts with full Stripe API access for testing without real transactions, while sandbox settings remain independent and production customer, product, and transaction data is not copied. A C# example uses Bogus to generate ten fake products and Stripe.net’s ProductService to create them with metadata in the sandbox, and the text notes that SDKs can populate additional account data. The containerized workspace uses Docker development containers, a .NET 8 image, Redis via Docker Compose, environment variables, VS Code customizations, and a post-create script that installs Stripe CLI. Configuration files can then be checked into source control, giving team members an isolated and consistent workspace for exploring payment workflows without affecting live data.
How OVO determined the right technology stack for their web-based projects
OVO faced maintainability issues caused by fragmented web technology stacks, including PHP, Vue, React, Nuxt, and Go, alongside outdated documentation. This fragmentation resulted in severe context-switching costs during code reviews and prolonged onboarding times for new engineers. To establish a single primary front-end stack, the team compared React and Vue against maintainability principles encompassing operability, simplicity, and evolvability. Vue was selected because its standardized framework structure and documentation minimized architectural variations across projects. Implementation entailed creating a standardized Vue boilerplate, updating the internal UI library, and scheduling periodic upgrades for legacy React services rather than migrating them entirely.
From Farmer to Security Engineer: How Dev Degree Helped Me Find My Dream Job
Cailyn Edwards recounts how she moved from leaving high school and running an organic farm to a career in infrastructure security through Shopify’s Dev Degree program. Before entering the program, she completed a horticulture co-diploma, finished high school and the required math courses, and pursued computer science while needing to pay her mortgage and maintain work-life balance. Dev Degree’s training path and rotating placements exposed her to computer science fundamentals, pair programming, Ruby on Rails on the orders team, infrastructure security, and network foundations, leading her to discover a strong interest in cyber security and cloud infrastructure. After graduating in September 2021, she joined Infrastructure Security full-time and later reports projects, internal security talks, a promotion to Senior Infrastructure Engineer, and Kubernetes contributions including a contributor award.
How Good Documentation Can Improve Productivity
Internal documentation is presented as a productivity and scaling tool for engineering organizations, especially as people move between teams, projects, or companies and remote work makes writing a default channel for knowledge sharing. Shopify’s approach combines standardized writing practices with three primary locations: Markdown microsites built with Docusaurus, internal GitHub for issues, READMEs, setup guidance, and searchable code, and the Vault, a GitHub- and Markdown-powered source of contextual information. The article argues that documentation should be treated as a product: it should be searchable, user-friendly, kept fresh, integrated into CI/CD, and hosted where engineers already work. It also recommends making writing routine through small contributions, paired writing, peer review, and audience-aware context, concluding that accessible documentation speeds onboarding, reduces duplicated problem-solving, supports asynchronous and cross-team collaboration, and improves developer literacy.
A Flexible Framework for Effective Pair Programming
Pair programming is presented as a mentoring and onboarding tool for early-career developers in Shopify’s Dev Degree program, where interns use it to build technical and communication skills. The author created a flexible framework to address progress tracking, session goals, a safe space, and communication, then refined it through an interactive RenderATL workshop with more than 30 attendees. The framework lets pairs choose roles, structure, agenda, environment, and communication practices; one described style assigns a driver to type and explain thought processes while a navigator reviews, observes, and suggests edge cases or refactorings, with frequent role switches. It also warns against hostile, passive-aggressive, and overly absolute language, and the pilot received positive intern feedback for supporting learning goals in a flexible format while continuing to evolve.
5 Steps to Bounce Back from a Negative Performance Review
An unfavorable performance review can feel like failing an exam, but it can also identify a clearer path to success when treated as feedback about role expectations rather than a judgment of personal worth. The five-step process is to avoid taking the review personally, adopt a growth mindset, clarify expectations with a lead, define measurable success, and establish a feedback loop. The author illustrates the approach with feedback about taking too long to ship code, which led to using smaller incremental improvements, and recommends tying goals to KPIs or other tangible metrics, supported by a lead or mentor. Regular check-ins, an up-to-date brag doc, and documented accomplishments can reduce surprises at the next review and help connect feedback to quarterly goals and observable progress.
How we automated FAQ responses at Grab
Internal engineering on-call engineers at Grab spent substantial working hours handling repetitive questions in Slack channels, such as how-to inquiries and access permission requests. To resolve this without building an in-house tool, the team conducted an anonymized vendor comparison and selected OneBar through an employee voting process and a phased proof-of-concept. Initial rollouts were restricted by contract to 20 channels, leading the team to prioritize deployment based on Slack message volume and member counts. Populating the knowledge base required roughly a quarter of consistent updates alongside tech talks, while a targeted crowdsourcing campaign among new onboarders expanded the glossary and grew usage to approximately 3,000 users.
Related topics
All topics →Weekly digest
The best engineering reads, once a week.