Stride for iOS

Content Discovery & Tracking for Businesses



An Increasingly Dynamic Workplace

Winning a sales deal requires a tremendous amount of energy and attention to the specific needs of the customer. So much so that the ones that turn out the best are a result of personalizing the solution to any exact measure. This approach comes with a tradeoff. Not all customers will experience this level of personalization. The time and resources it takes to tailor materials, documents and plans is difficult at scale. So how can companies edge towards this way of work? 

Product Marketers and Sales Ops work as quickly as they can to create content to equip their reps with the best information to cover as many use cases as possible. But getting that information out has its challenges:

  • There are too many files! Reps only needs to see the ones that are relevant to them.
  • Files living on corporate wikis grow stale immediately. They're also hard to navigate and require constant upkeep.
  • Producers can't control quality. Files get stuck in Email, Slack and local desktops which may not be the right version anymore.
  • Limited mobile support. Outside sales and executives are always moving and on site. 
  • Poor feedback loop. Which files are most popular and effective? How is the content performing in the field?

The issues and the opportunity isn't restricted with sales and marketing either. For customer centric businesses, these same strategies need better support. Account Management, Customer Success and Community can all benefit from a better way of work.

Folder trees may be fine for teams who collaborate together on files, but are not appropriate for publishing. Corporate wikis are uninspiring and hard to navigate. Mobile consumer experiences for content have come far, but lesser so for businesses. 

Folder trees may be fine for teams who collaborate together on files, but are not appropriate for publishing. Corporate wikis are uninspiring and hard to navigate. Mobile consumer experiences for content have come far, but lesser so for businesses. 


Personalizing The Corporate Web

Just like Google organized the World Wide Web and Amazon organized commerce, our mission was to organize institutional knowledge. Our strategy was to build on top of existing "sync and storage" services like Google Drive, Dropbox and Box, an intelligent layer that made Finding, Organizing and Publishing files smarter and more personal. Instead of going to an Intranet site, or an internal wiki which showed you the entire company's repository of stuff, you would only see what was most relevant for you, based on your projects, the people you worked with and topics that would make you most successful. Additionally, content creators would have the tools they needed to effortlessly maintain the freshness of their distribution channel and directly learn from the field how their content can be improved. Our basic model would be:

📄 File    🗂 Collections    🏢 Company


Designing for Relevance

Screen Shot 2016-03-27 at 6.55.49 PM.png

The first iteration of the product primarily focused on the needs of the individual content creator, say a Product Marketer. This included a way to find their files by Search and to stay on top of progress during document reviews. We included a tracking feature that would notify contributors when important files they cared about have been modified. This way there is no wasted time in coordinating efforts or writing an email stating the change. These features worked across all cloud services, Dropbox, Google Drive and Box. Whether people connected to one or all of them, the experience afforded increase control over file activity.

With search, each service offered different and in most cases, limited abilities to precisely find a file. Sometimes we don't remember a file by its name. Instead, we may only know the type, or who has worked on it. That led us to the design of a search experience that incorporated content type and people as filtering options. By doing so, people had greater flexibility in how they approached their search much more rapidly on desktop and mobile.

We were most excited about the additional of collections. They would play an important role in how content would be organized and also inform the underpinning logic for our DocumentRank concept. We started by allowing individuals to create their own collections to follow and curate files however they needed. Perhaps by topic, project, or even by person. This helped make tracking files and commonly accessed resources easier. It would reduce the number of times people having to ask around for a file or dig through the hairy trenches of an unfamiliar folder tree.

Collections were great for individuals and also teams. A shared collection was defined as a means to publish and host official documents that the entire organization could access. By doing so, Sales Enablement materials produced by Marketing and Sales Ops could better manage their distribution strategy. Files would be easily organized for teams, changes would instantly notify the sales force and reps could easily find what they needed right from their phones. The outcome was a transparent team with easier tools for accessing relevant information.

Build to Learn

Prototyping provides an invaluable ability to quickly learn and iterate on a design. Extensive use of InVision helped the team and I coordinate our energy and build a deeper shared understanding of the implementation.

Example User Flows


We opted for a traditional email and password authentication flow. It was a model that many people understood and allowed us to model our Domain Access Control rules based on company email addresses. We contemplated using one of the cloud accounts that people used to aggregate their files, but that proved to be too confusing to most people. The one downside to using email and password is the frequent forgetting of passwords that result in support tickets, despite having a reset password link.


Early on we discovered through conversations with users was the appeal of following their team member's activity. Using the same technology for saving search results, we designed a new flow to follow people to increase engagement. People would be able to look up email addresses of co workers because we had indexed the activity of files modified to improve the accuracy of identifying the right people to invite. The flow also included an optional step to personalize the message as they reviewed all the names of people they would be inviting. Some requirements were enforced like the domain needing to come from the company email address. The tradeoff constrained total number of potential invites, but kept the experience focused on team value.

Curation is a core aspect of the Stride experience. Content creators can post files that are final or approved to their respective Collections. These files then become available to everyone in the company. Team members are notified that a new document or a new version is available. We included a field for an optional description that clarifies the intent of the file for the rest of the company to see. Sometimes thumbnails are not informative or simply poor quality. With a quick swipe, a default graphic can take its place. Different graphics are available to categorically identify the document.

Ultimately, the intent of a collection is to be a highly curated and relevant source of information whereby team members can subscribe to. This way, sales teams can organize their enablement materials accordingly and product marketing has a direct line of sight to the preferred audience.  


Launched Features

Search w/ Top Contributors

Collections & Notifications

Add to Collection

Sharing & Slack Integration

Authentication Flow

On Boarding Flow

Additional features not show: Zen Reading Mode, Live Search Filters, File Tracking, More Notifications, Domain Access Control and Permissions, Email Notification Templates, Multi-Cloud Integration, Swipe File Shortcuts and DocuSign Integration.