Designing Apps for the Work People Really Do - Gartner (notes)

Gartner - Portals, Content and Collaboration
Brian Prentice
Brian Blau
Mike Gotta

Shifting software constraints = used to be expertise, then time and now design

Design considerations
1) relationships span devices, apps and applications
- designed for your closest network relationships
- eg - come get me, call me, i need advice "Circle of Six" app
2) social networking is a different type of purpose
3) Capture "in the moment, in the emotion" experience; people become active participants
4) Capturing product and service touchpoints must be kept simple.

Design decisions for "stick apps":
1) Three elements - categories, function, mechanics/flow.
2) Category - Frequency, loyalty, value, churn, necessary.
3) Function - sharing/social, emotion, reminders, interface, availability
4) Mechanics/Flow - pain points, notifications, personal cloud, gamification, task-centric
These elements drive engagement and retention.
Don't make bad apps better, just make good apps.
Eg - Zite and Path are sticky, core social experience, easy to learn, sophisticated content, constant change.

Clutter free interfaces - eg Paper app, Weather Dial app
App mechanics - eg - SongPop app, Cue app

Hard to program culture. 

Comments

Post a Comment

Popular posts from this blog

Enterprise Architecture Inside Salesforce

Image
  Enterprise  Architecture Inside Salesforce Enterprise Architecture — How We Do It Internally The two words, “Enterprise Architecture”, elicit various reactions — everything from “ we tried that and it doesn’t work ” to “ we need that! ” to “ we have an effective EA practice ”. Unfortunately it is possible (even easy) to do Enterprise Architecture  incorrectly , with an approach that is lethargic, technology-first and theoretical — the classic ivory tower. (In Salesforce, the internal IT group reporting into our CIO is called “Business Technology” so you’ll see me use BT to refer to Salesforce IT) I lead the Salesforce Enterprise Architecture team within Business Technology and I’m often asked the following questions: how does Salesforce do Enterprise Architecture? why do you need Enterprise Architecture? how do you shift the conversation to business capabilities? Illuminate — The “How” of Salesforce Enterprise Architecture Let me start with the “HOW” first. Within Sales...
Read more

Illuminate - Business Model Exploration

Image
  Illuminate — Business Model Exploration One of our world-class Salesforce Enterprise Architects, Jonathan Laudicina ( https://www.linkedin.com/in/jonathan-laudicina/  ) has done amazing work on Business Model Exploration. I want to highlight some of his work and I think you’ll find it useful. As a reminder, Illuminate is the Enterprise Architecture Methodology that we use inside Salesforce as well as with our customers. The overall Illuminate methodology is depicted below. You will notice that Business Model Exploration is the first step in Illuminate. Business Model Exploration is the methodology we use with customers to articulate: External Forces pushing on the business Internal Forces pushing on the business Customer specific Business Model Canvas At the heart of Business Model Exploration is the Business Model Canvas. It is the place in which you capture key factors about a company’s specific value proposition, partners, customer segments, cost structure and revenue str...
Read more

5 Key Components of a Successful Enterprise Architecture Function

  5 Key Components of a Successful Enterprise Architecture Function 5 Key Components of a Successful Enterprise Architecture Function Creating and managing a successful Enterprise Architecture function requires a variety of different hard and soft skills. In addition, each company is different and the Enterprise Architecture function needs to calibrate and align itself to the specific company. However, there are five common features of a successful Enterprise Architecture function that are applicable to all companies. 1. Governance Enterprise Architecture (EA) requires governance, however not in the form of complex documents, forms or processes.  Definitely avoid EA being seen as the policy-enforcement team — people will avoid EA if the perception is that EA is a blocker.  The best governance starts with a simple, recurring dialogue across multiple functions facilitated by EA. I am always amazed at how valuable it is just to get cross-functional teams to  talk . Pick...
Read more