How do we encourage and facilitate information sharing across Swedish Medical Group roles — providers, support staff and leadership committees?

Role: Researcher, UX designer, Project manager, Content strategist, Writer

Tools: Jive Software: Microsoft Project, InDesign, Excel

How we got here

I worked with SMG leadership, eHealth strategists, and Jive Software consultants to shape these goals for the DocSpot platform. 

  • Build connection and relationships among Swedish providers
  • Communicate and manage communications around a strategic direction
  • Share ideas and motivate learning of best practices
  • Help onboard new physicians and integrate new clinics


To gain broader buy-in from leadership, we ran a pilot with leadership committees who used DocSpot for their meeting agendas, shared resources, notetaking, and collaboration. The pilot included 550+ users and 2000+ pieces of content.

DocSpot processDocSpot process


Form contextual inquiries, I created 3 guiding personas: the experienced doctor serving on leadership committees, the clinic manager and a provider new to Swedish that helped guide pilot use cases and groups.

Persona 1:  experienced doctor serving on a leadership committee

Persona 2: a clinic manager

Persona 3: a provider new to Swedish

Information architecture

Based on what we heard from users, we knew we'd have to design a platform with a great deal of redundancy and multiple paths to reaching content. Users would need to understand what content types they could create and find from the get-go. We couldn't expect this audience to go through how-to tutorials. Searching and tagging would have to be robust enough to ease discovery.

I was responsible for creating seed content, training users on how to create pages and content, and collecting feedback that helped define the navigation, page components, and training materials we used. 

DS homepage wireframeDS homepage wireframe

The initial result of the pilot was a complex, diffuse site structure. Categories were difficult to define in this open and changing system. I was constantly revisiting and looking for ways to consolidate the 300+ groups and their group page components, layouts and permissions. It was a daunting, but rewarding weekly exercise. 

Group Template Strategy

Taking the learnings of the pilot, I created group page templates that be copied and pasted. Anyone using DocSpot could create and configure one of these groups. The group templates had uniform structures, layouts, and permissions — and made it easier to categorize and define use cases. It also allowed the platform to grow, and our small team to continue to manage and scale DocSpot to everyone in the Swedish system. 


I wore many hats on this project. I designed the information architecture, page, and content components of the experience, as well as acted as an internal project manager and community manager for the experience.

In the coordinated care model, providers treat patients as a team with the primary care doctor at the center. This team-based approach requires nimble ways of communicating while seeing patients. We met our goal of finding a more convenient than email for providers, clinic administrators, and medical group leaders to share their expertise, collaborate, and make care decisions more efficiently. 


Content strategy and adoption

An additional part of my job was to educate help to establish an approach for content creation in DocSpot. I built a lot of walk-around decks to help explain some of the underlying concepts of DocSpot tool, to train new users, and to advocate for adoption. 



No tool alone can change people’s behaviors and communication patterns. Just as it was important to understand how our users approached their communication technologies, it was also critical to understand the social and behavioral aspects of medical care. To design and implement a communications solution we also had to nudge providers accustomed to working independently to coordinate and make decisions as a team.

I learned that I loved the strategy, research, use-case definition, and designing DocSpot much more than the day-to-day community management and evangelism of the platform. I'm grateful that I had this opportunity to work on a team that had the autonomy and trust to experiment and move quickly. It helped us stay resilient and work quickly.

We did learn that we needed to slow down to concretely define strategic use cases, and couldn't rely on first-come, first-serve adoption. These use cases had to align with the goals of the tool, user needs, and the organizational priorities of project management and change facilitators in the Swedish system. 

I enjoyed the complexity of the healthcare space and the opportunity to bring a user-centered design approach to this project.