Digital Project Management Summit Notes

Jaimee Newberry


Rockin’ the Mobile App Space

  • Challenges
    • Jamie switched from web to mobile and found it difficult to speak about the technical aspects of mobile development like she’d been able to do for the web
    • Staying knowledgeable
      • recommends taking even the first few courses of a class or reading the first few chapters of a book about the technology your developers are using
      • being able to have a conversation; devs respect you more
      • know how to talk about solutions just enough, but don’t become prescriptive with developers
        • balance challenging a developer’s assumptions and being able to understand a potential solution and the logic behind it without telling developers exactly what to do, how to code, etc.
        • It’s ultimately the dev’s job, not the PMs, to determine the best dev solution
    • “Educating” client without intimidating (discussed how the concept of “educating” a client is inherently condescending)
      • Make everyone feel involved
      • Monitor your word choice
      • Pull in help from your team (find the designers and devs who can also explain without being condescending)
    • Stick to high level discussions with client and let the team deliver a solution
      • Bridge example from Jared Ponchot – the client may have decided they need a bridge but when you get to the underlying problem there may be some other way to solve it (a better way to get across the river, a way to meet needs without crossing the river)

A PM removes obstacles


  • A PM removes obstacles
    • A PM’s job is to help the team delivers solutions; gather the materials and facilitate the communication necessary for delivering those solutions
    • When I’m double booked for meetings, or don’t know which task to start first, or am not sure how to approach a problem this will be my guiding principle


Micro takeaways[AJ1]

  • Discuss content
    • Consider microcopy: Twitter’s “What are you doing?” became “What’s happening?” which is less personally intrusive and opens the possibilities for what to tweet about (anything going on near by that might be interesting vs. what I’m doing that might be uninteresting or too personal)
  • iPhone first because Apple’s guidelines help drive design and development; Android design second
  • Remind clients that a Universal app for both iphone and iPad should include two separate apps that are sold in a bundle, not one app with one development cost
    • One app might not suit the use context and capabilities of each device


Mentioned Mark Kawano, former UX evangelist at Apple, as a mobile UX resource @markkawano

Back to Digital Project Management Summit