Ginkgo

Helping BID directors turn fragmented data into outreach plans

I led the design of an AI-assisted reporting workflow for a GIS and CRM platform, guiding users from raw neighborhood data to a decision-ready plan.

AI Product DesignGuided WorkflowsUser ResearchProduct Strategy
Ginkgo AI report dashboard on a laptop
Role
UX/Product designer
Company
Ginkgo, GIS + CRM platform
Timeline
March – August 2025

Outcomes

Shipped
AI-assisted reporting MVP that layers insights over raw data
Validated
AI reporting as a premium-tier feature in user testing
Established
A scalable design system to support ongoing product growth
01 · Context
The product

Ginkgo is an app that integrates geographic information systems (GIS) with CRM, enriching neighborhood data and generating reports to guide decision-making for business improvement district (BID) staff.

What I owned

I led the design of an AI-assisted reporting workflow to help BID directors turn fragmented data into actionable outreach plans, from research and framing through a prototype tested with users.

Current state

BID staff need to create actionable plans from reports

The app’s confusing UI/UX and lack of workflows present roadblocks.

Diagram of the planning tasks BID staff juggle: contacts, email, scheduling, tasks, integrations, and outreach
User challenges

What users had to do

  • Jump between maps, reports, and external files
  • Manually interpret results
  • Translate report data into plans outside the app
Ginkgo reports list and map layers screens users jumped between
Confusing landing page UX

App login, then no report guidance

Original Ginkgo map view with no report guidance after login
  1. Fragmented entry points

    BID staff didn’t know what to do after logging in.

  2. No intent framing

    The workflow was limited to on/off settings.

  3. Data without synthesis

    Report creation was confusing and basic.

Pinpointing the opportunity

Ginkgo surfaced data, but didn’t help BID directors plan outreach

BID directors could find maps, records, and reports across Ginkgo, but had to manually connect these pieces to form an outreach strategy. This created friction, slowed down decision-making, and limited the value users got from the platform.

  • Data lived across maps, records, and reports with no unifying workflow
  • Users had to export or manually synthesize information outside the product
  • The app answered “what exists” but not “what should I do next”
Solution framing

BID directors are responsible for turning data into real-world action

BID directors are often under-resourced and time-constrained. They need tools that help them move from raw information to actionable plans, especially when coordinating across stakeholders, timelines, and neighborhoods.

  • Plan and justify outreach efforts to boards, cities, and stakeholders
  • Identify priority areas, trends, and risks quickly
  • Translate complex data into clear recommendations and next steps
02 · Process
The solution

Proposed workflow

1
Home page
Report creation starts immediately after login.
2
Guided workflow for report setup
  • 3 criteria questions
  • 1 goal-based question
  • 2 refinement questions
3
AI report
  • AI insights and suggestions
  • Raw data infographics
  • AI query field
Key additions that structure intent and enable AI insights and interactivity in the report
Guided workflow

Login, then report setup immediately

Guided report setup screen with Mad Lib style prompt
  1. Intent framing

    Eliminated report-creation guesswork in favor of guided prompts with a defined report goal. Increased clarity and set up the AI insights.

AI report

Report with AI integration

AI-assisted outreach report with insights, recommendations, and query field
  1. AI-assisted report

    Raw data output enriched with AI insights above it, and a query field below.

Workflow summary

From guided setup to a regenerable report

Five-screen flow from report setup through AI-assisted report output
  1. Report setup

    A Mad Lib style prompt guides users through previously complicated menus (screens 1–4).

  2. Report output

    AI integration lets output and insights be regenerated on the fly (screen 5).

Design decision

Prompt setup: open prompt versus guided sentence

Free-form text input didn’t seem like it would solve user needs or improve the UX as much as inputs within a Mad Lib style prompt.

Open chat prompt compared with the chosen guided sentence setup
Design decision

Split-page report + AI versus full-page report + AI

AI in a side panel next to the report compared with AI insights placed within the report
AI side-by-side

OK, but less direct.

AI within the report (chosen)

Stronger connections to the raw data.

Solution hurdles

Engineering constraints shaped how the solution could be delivered

The concept required restructuring report creation and layering AI into the output, but major architectural changes weren’t possible. So the design strategy had to work within existing systems while still creating enough customer value to justify a premium tier.

Constraints
  • Engineering bandwidth was limited for custom development
  • The Omni reporting plugin defined how reporting could be extended
Workarounds
  • Extended functionality within Omni instead of replacing it
  • Leveraged AI APIs to deliver insights without altering core architecture
  • Positioned AI-assisted reporting as a premium feature to support integration costs
03 · Outcome
User interviews

User interviews revealed distinct needs based on experience level

I interviewed users about their work roles, tasks, and app needs, along with a Q&A about my prototype. This surfaced two usage patterns: newer users who needed structure to get started, and experienced users who wanted fast, flexible control. This informed how workflow guidance and AI capabilities were positioned within the product.

  • Newer users valued guided workflows that reduced ambiguity
  • Experienced users preferred fast access and selective AI usage
  • Validation supported guided setup for onboarding and AI synthesis for power users
What I learned

Guided setup and AI each contributed value

Interviews revealed that structured prompts helped users articulate what they wanted to analyze, while AI-generated insights accelerated synthesis and decision-making. Together, these patterns supported offering guided workflows as core value and AI-powered reporting as a premium capability.

  • Guided Mad Lib setup helped users frame intent and reduced setup ambiguity
  • AI-driven reports provided the most value by synthesizing raw data into insights
  • Validated positioning AI reporting as a premium tier due to its differentiated impact
What the prototype delivered

The prototype delivered core functionality and validated the business direction

The prototype enabled structured report creation and layering of AI insights in a way that worked within technical constraints. This allowed testing of real user workflows, evaluation of pricing strategy, and a foundation for future product expansion.

  • Introduced AI-assisted reporting to generate insights alongside raw data
  • Confirmed that AI features supported a premium-tier pricing model
Impact

The solution improved user workflows and differentiated the product

The updated reporting experience reduced friction for new users, accelerated decision-making for experienced ones, and positioned Ginkgo as more than a data repository. These improvements strengthened user perception and created strategic room for premium features.

  • Guided workflows clarified how to create reports and reduced setup confusion
  • AI-assisted output enabled faster synthesis and reporting compared to manual methods
  • Strategic differentiation moved the platform toward insight-driven decision support
Next case study
Siemens
Optimized product evaluation (+12%) and purchase (+4%) of SaaS products
View Case Study →