Cover-photo-2015-10-07_21_29_23__0000-332920151007-3-1y5vc6n
Lee Munroe

Lee Munroe

San Francisco Designer. Developer. Product Maker. Joined almost 5 years ago via an invitation from Jeff B. Lee has invited Ronan Flynn-Curran

  • 31 stories
  • 52 comments
  • 35 upvotes
  • Posted to What's your team's design stack?, in reply to Mitch Malone , May 30, 2018

    Wasn't familiar with Whimsical. Looks good.

    How do you find keeping Storybook aligned with what's documented in Confluence (and vice versa)?

    0 points
  • Posted to What's your team's design stack?, in reply to Ronan Flynn-Curran , May 30, 2018

    Love Niice.co

    0 points
  • Posted to What's your team's design stack?, in reply to Ronan Flynn-Curran , May 30, 2018

    Abstract is great. Central to our workflow now. Lingo is a solid tool but it does something which I would expect Sketch to already do, which is shared layer and text styles as part of a library. Before Sketch libraries we also used Lingo to share our UI components.

    0 points
  • Posted to A simple and minimal to do app. , in reply to adrian io , May 03, 2018

    It didn't make any money, and I wasn't confident that it could (without a lot more work). Had a decent amount of users and attractive domain name. Sold it with Flippa.

    0 points
  • Posted to A simple and minimal to do app. , May 03, 2018

    This is cool, and a great way to experiment, exercise your design skills and learn new technologies (Vue.js in this case).

    I made a similar "yet another todo app" a few years ago (https://flask.io) to learn some Rails and jQuery. Ended up getting some (just a little) traction which enabled me to use it for experimenting with analytics tools. I ended up selling it a few years later.

    So even though this has been done before, great work shipping a functional product.

    1 point
  • Posted to Our Product Design Workflow for Designing Enterprise Software, in reply to Mattan Ingram , Dec 07, 2017

    Hey Mattan, I agree. This isn't truly agile or truly waterfall, but somewhere in the middle.

    Due to our current process (where we focus on several big features per release) there is a lot of iteration at the design and discovery phase which involves engineering leads. Sometimes this will include coded prototypes to validate things work as intended.

    Once we move into the "develop" phase, you're right we continue to learn more and have to make changes, but we have hopefully massively decreased the risk of big changes at this point. Often during development, depending on the project, we'll have several micro design iterations.

    0 points
  • Posted to Our Product Design Workflow for Designing Enterprise Software, in reply to Matt Basham , Dec 07, 2017

    Thanks Matt

    0 points
  • Posted to Our Design Team's Process for Running Usability Tests Every 2 Weeks, in reply to Charles Pearson , Jul 03, 2016

    Thanks Charles.

    0 points
  • Posted to Our Design Team's Process for Running Usability Tests Every 2 Weeks, in reply to Megan Vo , Jul 03, 2016

    Thanks! I find it helps provide some context for when sharing our reports. Helps those reading the report visualize who was testing it. Also helps me when I'm looking back at previous reports, seeing a photo can help me remember the user and what we chatted about.

    0 points
  • Posted to Our Design Team's Process for Running Usability Tests Every 2 Weeks, in reply to Sherizan Sheikh , Jul 01, 2016

    Good question. Since the report is in our Wiki, we use inline commenting to have discussions around each issue and pull in the relevant PM, lead developer or lead designer. Out of that we either modify our designs and prototypes, if it's something we're working on, or if it has already been built create an issue for developers to look at (we use Jira). If it's something major then we'll pull in relevant team members and discuss over a whiteboard.

    Also worth noting we tag our usability test reports in a way that they are pulled in to product requirement wikis, so hopefully they are always referenced even in future projects.

    0 points
Load more comments