Serve IT · Aug 2025 to Dec 2025 · Case study
Greater Bloomington Chamber of CommercePages designed with staff
Bloomington Chamber of Commerce Serve IT work. I designed around the staff who have to find, update, and keep the pages moving. A useful interface gives them control instead of making them decode the builder's decisions.
Who it is for: local businesses using the pages, and staff who have to keep them. What I did: designed the pages with staff. Still open: the semester write-up is not filled in yet.
This page is long because the rubric asks for every row. The semester detail is not filled in yet. Empty rows stay marked ... a blank is more honest than a story I don't have yet. Where the public-safe write-up needs a boundary, you will see an honest scope note. I would rather leave a blank than invent a metric or a quote.
01 · 5 pts
Introduction / professional profile
Who you are
Jade Zhao. Informatics student at IU Bloomington Luddy (May 2027). Student Digital Humans project lead. Laurie Burns McRobbie Serve IT Clinic, Jan 2024 to present. Clinic work for partners whose staff keep the page after students leave. On this term I designed Greater Bloomington Chamber of Commerce pages with staff.
Your area(s) of interest
Digital Humans, human-centred AI, UX (user experience), and business technology. This case study is the fall 2025 Chamber term.
Your technical strengths
Designing pages with staff, so someone could find what they needed, and so staff can keep the pages after students leave. The full list is on Serve IT.
The kinds of work you want to do
GTM (go-to-market) engineering, AI product, and solutions work. Digital Humans is the project I keep studying. I only write down what has actually shipped.
Links
02 · 5 pts
Project overview
Problem statement
Local businesses use these pages. Staff have to keep them. If a page is designed without the people who will run it, nobody can find what they needed, and nobody can keep it. I designed the pages with staff. Rows that aren't written yet are marked under Process, Deliverables, and Reflection.
- Dates
- Aug 2025 to Dec 2025. [still writing: exact kickoff and handoff dates from that semester]
- Team
- [still writing: team names from that semester's roster]
- What the team as a whole was asked to do
- [still writing: the semester brief, once it is safe to publish] True line for now: pages for local businesses, designed so staff can keep them.
- What my part of the work entailed
- I designed the pages with staff, so someone could find what they needed.
03 · 5 pts
Client description
Client: Greater Bloomington Chamber of Commerce. Agency website: https://www.chamberbloomington.org/. Their public site presents the Chamber as supporting local businesses in Bloomington, Indiana. Local businesses use the public pages. Staff have to keep them.
1. What the client wanted
[still writing: quote or paraphrase from the semester scope once it is safe to publish] True line for now: pages designed with staff, so someone could find what they needed.
2. What problem you tried to solve
[still writing: client-stated problem in their words] True line for now: local businesses need pages they can use, and staff need pages they can keep.
3. The process you went through to reach the final solution
[still writing: short process summary once the design notes with staff are written up] See also the labelled rows under Process / how you worked.
4. What that final solution is
[still writing: which pages you designed with staff] True line for now: pages I designed with staff, so someone could find what they needed.
04 · 5 pts
Process / how you worked
True boundary for every row below: I designed pages with staff. Staff have to keep them. The semester detail is not filled in yet.
Research
[still writing: stakeholder research notes / public-safe summary]
Data collection
[still writing: what you learned from staff about what people needed to find]
Accessibility assessment
[still writing: accessibility checks if you did them on this project]
Wireframes
[still writing: wireframes if you made any with staff]
Agile / sprint workflows
[still writing: how the team organised the weeks]
Testing
[still writing: how you checked that someone could find what they needed]
Iteration
[still writing: what you changed with staff before the term ended]
Technical decision-making
[still writing: technical choices you can name in public] Boundary that stays firm: staff have to keep the pages.
05 · 5 pts
Tools and technologies
Only real lines where confirmed. Unconfirmed tools stay marked.
- Figma
- [still writing: name the tool if you used it]
- Tableau
- [still writing: name the tool if you used it]
- GitHub
- Real for this portfolio: github.com/jadexzhao versions the public case study page.
- Excel
- [still writing: name the tool if you used it]
- Accessibility tools
- [still writing: name the tool if you used it]
- CMS platforms
- [still writing: name the tool if you used it]
- APIs
- [still writing: name the tool if you used it]
- Microsoft Planner / Teams
- [still writing: name the tool if you used it]
06 · 10 pts
Deliverables / artifacts
Security-team documents must keep client privacy. Block out or remove client names and website mentions on any item shown. On this public page, do not paste private scope text, vulnerabilities, or non-public names. Greater Bloomington Chamber of Commerce is the public project name and is fine.
Screenshots
[still writing: public-safe screenshot]
Dashboard images
[still writing: dashboard image if used]
Wireframes
[still writing: wireframe or annotation if used]
Reports
[still writing: design notes from working with staff]
Code snippets
[still writing: code snippet if relevant]
Data visualisations
[still writing: data visualisation if used]
Videos / demo links
[still writing: video or demo link if used]
Presentation slides
[still writing: presentation slides]
Before / after comparisons
[still writing: before / after if a public-safe pair exists]
Testimonials or client feedback
[still writing: attributed quote with permission, in quotation marks]
07 · 10 pts
Final reflection
The semester detail is not filled in on this page yet. Empty rows stay marked until the notes are real.
What you learned
[still writing: what I learned]
Challenges encountered
[still writing: challenges encountered]
What you would improve
[still writing: what I would improve]
Team communication lessons
[still writing: team communication lessons]
Ethical considerations
[still writing: ethical considerations]
Technical growth
[still writing: technical growth]