Insurance Is Complicated

Mapping and redesigning the broker insurance enrollment experience — Candor USA

Source: squarespace-export/images/insurance-is-complicated/001.jpg–026.jpg (26 slides, mostly diagrams not prose). Work done at Candor USA.

Suggested title & subtitle

Title: Insurance Is Complicated Subtitle: A UX and service-design case study for Candor USA — mapping the end-to-end broker/employer insurance enrollment journey, benchmarking competitor tools (Ease, FormFire, HealthSherpa, Simply Insured, eHealthInsurance, Applied Epic) against a SERVQUAL service-quality framework, and translating customer research into two shipped products: the Candor Digital Briefcase and a Call Center Training Tool, inside a unified "Candor Unified Benefit Ecosystem" platform architecture.

Important note: this case study is almost entirely diagram-driven (flowcharts, Sankey diagrams, service blueprints, C4 architecture diagrams) — there's very little free paragraph prose to lift directly. Recommend the rebuilt page leans on recreated diagrams, using the verbatim survey statements and feature-commitment statements below as the actual "research voice" text blocks.

A. Current-State Journey Map (slide 001)

Large vertical journey/flowchart tracing a prospective customer/broker from marketing contact through full enrollment — the "before" picture behind the case study's title. Phases: Marketing Campaigns → Lead Generated → Lead Entry (Pre Condor Engagement / Candor Engagement / Data Entry / Selection Phase / Processing Phase) → 4a. Underwriting Process (First Contact / Data Entry) → 4b. Fully Insured (Selection Phase / Confirmation Phase) → 5. Enrollment (Enrolled Phase).

Embedded decision-tree questions: "Should our message be controlled by the salesperson?" / "Should our message be controlled by the associate?" / "What customer information?" / "Should Candor be represented in sales activities?" / "Should we ask for a customer's consent to use some information?"

(Fine-grain step labels along the main spine were too small to transcribe reliably — recreate the phase structure, not every node.)

B. Competitive Benchmarking — Usability & Service Blueprints (slides 002–003)

Slide 002 — Sankey diagram: Usability ratings (1–7) → Subject (Candor, Ease, Easy App Online, FormFire, HealthSherpa, Simply Insured, ehealthinsurance) → Features (Broker Reports, Community Rated Plans, Direct Upload Documents, Employee Portal, Enroll Clients, Full Carrier MKT, Level Funded Plans, Make Payment, Online Level Funded Application, Portal Renewal, Quick Quote, Self Enroll, Selfservice Change, Single Plans, Small Business Plans, Spreadsheet Upload, Third Party Integration). Candor's flow concentrates around rating "4" with some reaching "7"; Ease and FormFire spread wider.

Slide 003 — Three service blueprints (FormFire, EASE, Easy Apps Online), each with swimlanes: Physical evidence / Customer actions / Onstage contact actions / Backstage contact actions / Support processes, actors Broker/Employee/Employer.

FormFire: Lead, Broker Dashboard, Employee Census, Employee data entry, Broker Service Tracked, Employee sees welcome letter, Other condition, Broker checks participation, Plans and pricing, Health Insurer available for Employer, Health Quotes for Employee.
EASE: Broker sets up log in, Employee Log in, Employer Dashboard, Employer Log in, Profile Pages, Employer Docu-sign, Time frame notification, Group starts to review, Health Quote available for Employer/Employee, Employee signs, Broker/Employer Dashboard.
Easy Apps Online: Step 1–4, callout "At this point everyone is enrolled in health coverage."

C. Research Framework — Service Quality Model (slide 004)

Four circles — Reliability, Personal Attention, Comfort, Features — feed into Service Quality → Customer Loyalty. Citation: Dabholkar, P. A., Shepherd, C. D., & Thorpe, D. I. (2000). A comprehensive framework for service quality: an investigation of critical conceptual and measurement issues through a longitudinal study. Journal of retailing, 76(2), 139-173.

D. Customer Research Findings — 17 SERVQUAL statements (slides 005–007)

Reliability

When Candor's employees promise to do something by a certain time, they will do so.
When Candor's employees promise to do something in a certain way, they will do so.
Candor will maintain error-free records.
Candor will perform the service right the first time.
Candor's interactions with you will be consistent.

Personal Attention 6. Candor's employees will give you personal attention. 7. Candor will tell you exactly when services will be performed. 8. Candor's employees will never be too busy to respond to your requests. 9. Employees of Candor will be courteous with you. 10. Employees of Candor will be willing to help you. 11. When you have a problem, Candor will show a sincere interest in solving it. 12. Employees of Candor will give prompt service.

Comfort 13. Employees of Candor will have the knowledge to answer your questions. 14. Candor's employees will have the ability to solve your problems. 15. Candor's salespeople won't pressure clients into a plan that wont fit their needs. 16. The behavior of Candor's employees will instill confidence in clients. 17. You will feel safe in your transactions with Candor.

(The fourth dimension, "Features," isn't given its own 1–17 list — it resurfaces via the stakeholder feature-commitment items 18–21 below.)

E. Competitor Business Model Analysis — HealthSherpa (slide 008)

Relationship map: Carrier A/B/C, Brokers, "HealthSherpa is free."

Carrier A ↔ HealthSherpa: "Give them bodies" / "Appoints Health Sherpa to sell" ($)
Brokers → Carrier A: "No Appointment"
Brokers ↔ Carrier B/C: "Provides grass route marketing" / "Appoints Broker to sell plans"
Brokers ↔ HealthSherpa: "Gets clients info provide boots on the ground" / "Client management software"

Callout: "Health Sherpa's business model is banking on the fact that brokers are not appointed with all carriers and HealthSherpa is."

F. Defining Requirements — Feature Commitments by Stakeholder (slides 009–012)

Employee Focus Features 18a. Candor will provide a Intuitive profile creation portal. 19a. Candor will provide a single channel for employee data entry. 20a. Candor will provide high quality content. 21a. Candor will produce a employee advocacy output.

HR Focus Features 18b. Candor will provide an Intuitive employee data management channel. 19b. Candor will provide low friction channel for employee data collection and transfer. 20b. Candor will provide an easy benefit management platform. 21b. Candor will produce optimized plan recommendations.

Broker Focus Features 18c. Candor will provide an intuitive client management portal. 19c. Candor will provide levels of automation for brokers. 20c. Candor will provide a near frictionless carrier submission process. 21c. Candor will provide tools for brokers to gage and strategize for their business.

Internal Candor Focus Features 18d. Candor will provide metrics for the performance of (personal attention, comfort, features, and reliability). 19d. Candor will measure levels of customer loyalty. 20d. Candor will automate service failure measure. 21d. Candor will work with hr tools such as Paylocity.

These map to the ecosystem's four main product/user tracks (Employee, HR/Employer, Broker, internal Candor ops).

G. Research Synthesis — From Survey Items to Design Clusters (slides 013–015)

Slide 013 re-shows the Slide 004 diagram with Reliability/Personal Attention/Comfort circled (Features excluded) — "we're focusing on these three."

Routine Knowledge-base (slide 014) — derived from statements 2, 5, 13, 16, 17. Communication Study (slide 015) — derived from statements 5, 6, 9, 10, 8, 16, 17.

This re-clustering is the analytical pivot of the case study, directly motivating the solution below.

H. Solution — The Call Center Training Tool (slide 016)

Circular-flow process: Training is scheduled → Parties create training program → Training conducted → Study folder created ("triggered by the completion of a training session with team members") → Team members conduct customer service → acquire transcription → Run Frequency → Excel Template created ("will show: Word shifts between training periods. Member vocabulary evolution. Weigh against group finalize to call made ratio.") → Results attached to Excel sheet with meta-data (Call Name/Date/Time/Duration/Etc.) → Parties evaluate results → Parties create strategy for future training cycle ("Any changes in process and message will be added to the next training cycle agenda.") Callout: "Any changes made in strategy at this point will skew results unless otherwise accounted for by creating a augmented study folder."

Mechanism: training sessions are recorded/transcribed; transcripts + metadata feed an Excel template tracking word-choice shifts and vocabulary evolution between training periods, weighed against a finalize-to-call-made ratio; results feed a continuous evaluate-and-adjust loop.

I. Competitive Benchmarking — Information Architecture / Sitemaps (slides 017–019, + 026 appendix)

Three near-identical-format sitemap trees for Candor, FormFire, and HealthSherpa broker portals (each rooted at "Broker Landing Page"), plus a fourth appendix sitemap for Applied Epic (slide 026) benchmarked separately. Useful as a side-by-side competitive teardown graphic rather than prose — full node lists preserved in the raw transcription if needed.

J. System Design — Personas, Ecosystem & Architecture (slides 020–025)

C4 notation legend (slide 020): Stakeholder, Staff, Mobile Container, Web Browser Container, Software System, Container Database, Existing Software System, Relationship, Component, Expanded Container.

Personas (slide 021):

Association Members — "A customer group that is part of and comes to us from a association."
Broker — "A customer that has a license with Candor"
Business Owners — "A costumer group that comes to us outside of an association."
Agency Manager — "A customer managing several brokers within the candor license"
Business HR Manager — "The person in-charge of HR within the group"
Employee — "An individual within a group"
Carriers — "Company that holds insurance policies"
CSR (added later, slide 024) — "Interact with customers to handle complaints, process orders, and provide information about an organization's products and services."

Candor Unified Benefit Ecosystem (slide 022): central system box — "Allows stakeholders a end-to-end benefit experience. (Management, Sales, Advocacy)" — connected to all personas plus Ring Central ("Provider of cloud-based communications and collaboration solutions for businesses" — "Costumer call and messaging management"), Vericred ("Digital Distribution Of Health Insurance and Employee Benefits"), ZOHO ("Manages a company's interaction with current and potential customers" — "Procedure and pipeline management").

API Application architecture (slide 023): product suite (Employer Stargate, Employer Anubis, Employee Anubis, Digital Enhanced Agency, Candor Digital Briefcase, Candor Cross Sell Portal) → shared API Application layer → central Database. Products:

Employer Stargate — "Self-service portal with the ability to, enter data, enroll, purchase etc"
Employer/Employee Anubis — "Employee individual information center, communication channel, & data entry channel"
Digital Enhanced Agency — "Agency management platform (Business analytics and automated SERVQUAL procedure and metrics)"
Candor Digital Briefcase — "Broker Focused tooling (Client management automation, Record keeping, communication channel …)"
Candor Cross Sell Portal — "Broker platform for individualized full life coverage. Short Term Disability Insurance, Long Term Disability Insurance, Retirement"

Product index (slide 025): clean summary grid of the above seven products with their one-line descriptions — good as a "the products we built" section.

Flags for the rebuild

Slide 001's fine-grain journey map detail wasn't legible at available resolution — recreate the phase structure, not every node, unless a higher-res source exists.
Multiple original typos preserved verbatim throughout (a Intuitive, wont fit, costumer, SERQUAL→SERVQUAL, a augmented, Templet, gage, grass route) — developer should decide whether to clean these up or preserve as authentic voice.
Slide 026 (Applied Epic appendix) reads as an afterthought placed after the system-architecture section rather than next to the other competitor IA slides (017–019) — consider moving it.
"Features" as a SERVQUAL dimension never gets its own 1–17 list like the other three — only resurfaces via the stakeholder items 18–21.
Almost nothing here is prose to lift directly — budget real design/development time to recreate the diagrams (journey map, Sankey, service blueprints, SERVQUAL circles, training-tool flow, IA sitemaps, C4 architecture) rather than expecting to just paste in text.