Architecture for a New Platform
Prior to my involvement with Ambi, the information architecture alongside desired feature-set were set and established via collaboration with design firm MetaLab. Further refinement was done later during my time at Ambi in collaboration with the firm SGTM to help establish the core architecture and philosophy of Ambi.
Most notably, was the decision to move Ambi away from its original vision of single silos run by individual institutions into a centralized network with walled 'Communities' which serve as keys for Users. So long as a User is a member of a Community, they can access exclusives Groups and Spaces within that Community. This allows Users of Ambi truly own their account, and easily navigate to and from institutions.
The initial feature-set was brainstormed through workshops and multitudes of back-and-forth client and user engagements, then implemented and rolled out to our initial clients.
Paring Down Features
These initial plans and implementations at Ambi were focused primarily on giving tools to turn Ambi into a combined user experience. This included a broad set of features including profile feeds, file storage, chats, calendars, etc. We had implemented these broad assumptions early on regarding the feature set Ambi should have.
Over time and as feedback started rolling in from more users, it became obvious resources could not maintain this wide breadth of tools as well as some features simply not being used either from lack of required depth or a miscalculation on the inherent value of the feature early on.
The decision was made, then, to retire some features and bring the platform down to a core set to build upon.
We decided on a different approach from our usual research subjects of students or instructors and interviewed Student Leadership themselves to discover their biggest pain points in engagement and information dissemination as it was discovered that they often are the faces and troubleshooters of many institution's online engagement sectors.
"Our fraternity has two Facebook Groups, one official and one sorta run on the side that sometimes plans non-sanctioned events and such. This is a problem since the school kind of treats both as under us, so we have to monitor god knows how many channels in case someone does something stupid."
"It's pretty hard getting information out to everyone since there isn't really one place for it. Kinda just have to tell as many of them as we can on campus or on the Facebook Group and usually it spreads from there."
It became pretty clear that Groups, or Spaces were a large desire for these Leaders to both disseminate information, socialize online, and to maintain official oversight. Going forward, this would be the new structure for Ambi.
A New Iteration
The latest step then was to restructure the platform. Making use of the existing style guide provided by earlier collaborations with MetaLab as a base and updating it, it was time to design the updated Group-Centric base for Ambi