FactSet Shareholder Meeting Report
the problem
Nikon has an iPhone app that can use the Wifi it it’s dSLR and mirrorless cameras. Personally, I’ve felt this could use work as it is slow, has an old UI, and doesn’t map to modern photographer workflows. Since this was my personal opinion, I knew I had to engage other users to validate my assumptions of this being a problem. So, I spoke with other photographers and people on the street to find out what they wanted in a complimentary app for their camera.
The original report used an old acquired UI and the user had to touch multiple elements to pull meeting data together.
Users had to wade through a company profile and historical data to drill into their desired meeting’s details.
Meeting details had no context or historical reference, only a simple table of proposal vote counts.
The breakdown
After talking to about 23 people, I broke down the user into two groups:
The casual user - doesn’t know too much about their camera and most likely has a kit lease and crop sensor camera. This person didn’t know the app was available or how to use it. They just relied on using the SD card to transfer files to their computer. From there, they didn’t use CaptureOne or Lightroom. Maybe they used a free program but they didn’t have much in the way of an editing workflow.
The pro user - These were people who knew their camera, knew the settings, and had multiple lenses. This user had a lot to say. They lamented the loss of the SD card slot on their MacBook Pro, they had a workflow from camera to develop, to retouch, to client/web. This user didn’t like the Nikon app because it didn’t help them their work, in fact - it just slowed them down.
From here, I decided to focus on the pro user. I also wanted to understand their workflow a little better. I knew mine, but I need to validate assumptions here. I was a camera -> Lightroom Desktop -> Photoshop -> client/Instagram person, but were other users the same?
The main objectives of the users were spread out across multiple applications and workflows.
We worked together to define a workflow starting with looking up a company. The users were predominately asset manager and hedge funds tracking a particular company.
The solution
I made several versions in Axure to test with users and evaluate the information architecture. We eventually settled on four tiles that break down the report while allowing users to drill down or traverse relationships.
I also visualized as many data points as I could without creating a carnival effect. This was to allow scan-ability while drawing users into deeper data.
Initial wires in Axure take form around tiles separating the different aspects of a shareholder meeting
Data hierarchy is refined with some additions to the individual sections.
results
Testing of the MVP showed users liked the layout and were particularly fond of the visual data points. The ability to drill down into data or jump to related data was also mentioned as a high point. The best KPI was usage of the old reports dropped significantly when this was rolled out. FactSet was able to sunset old reports, support, and resources since our user workflows were supported in one new application.
Unfortunately, technical limitations did not allow for developers to create the network map of board relationship, but that is planned for a future sprint.
The first version was released with high-value, low-effort features as we gain more user feedback on the future direction.
High level trends with simple visualizations take up the first tile. The user has access to more details via the info boxes within each tile.
Proposals and source details are available for the user to drill down into. Exact proposal and meeting text was available for further analysis and context.
Vote breakdowns were available for any proposal in a contextual box on click.
Board sentiment, bios, and relationships are available in the directors section. The user can also see voting activity by ownership blocks with activism ratings.