Applying Lean UX to Capital Markets - Lessons From a Year of Lean UX on Wall Street

The Lean UX approach to interaction design is a spectacular model for defining and implemented what is needed in appications to support the users in their jobs, as compared to technical deliverables that in the end often do not meet the needs of the users.  In this talk, I will go over strategies for applying lean UX practices to capital markets projects, adapting UX to agile processes, including executing user interviews, rapid UX design, mockups to UI prototypes, and rapid implementation through continuous delivery and end user experience / acceptance testing.

 
3 favorite thumb_down thumb_up 7 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

I will lead the session through a scenario based discussion of a project I have lead implementation of over the course of 2013 to build a next gen trading platform for a major investment bank.  During this I will cover:

  • Lean UX in a nutshell - why should I care?
  • Framing a vision of how the user eperience will enhance the business
  • Determing which ideas are valid through creation of Minimum Viable Products
  • Thinking like a user as well as a designer
  • Conducting user interviews to develop personas
  • Storyboarding and wireframing user experiences
  • Translating user storyboard and wireframes to code
  • Continuous user review to keep the voice of the customer through the project lifecycle
  • Rapid and continuous realases and user acceptance testing

Learning Outcome

There are many valuable take aways from the session, including but not limited to:

  • The importance of Lean UX to your project
  • Understand the organizational shifts necessary to integrate Lean UX
  • The important of defining the Minimal Viable Product required for delivery
  • How to schedule MVP's across tasks in the software process, and
  • How to integrate UX and Agile into successful software delivery

Target Audience

Developers, Project Managers, Interface Designers, Operations / Support Staff, CxO

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Sachin goel
    By Sachin goel  ~  3 years ago
    reply Reply

    Hi

    Will there be learnings from this session which will be beyond capital market, which audience can take away and apply?

    I see Lean UX an effective measure in projects where workflows are complex or business process itself is evolving and hence no right / wrong scenario.

    thanks - Sachin

    • Michael Heydt
      By Michael Heydt  ~  3 years ago
      reply Reply

      Yes, it will have take aways form non-capital markets.  That just happens to be the environment that I work in, and one where I have not seen much adoption of the practices.  One of the things it has been really successful at is related to your comment of constant evolution of process.  One of the things I did first was define a very good business strategy that the overall lean ux process would provide to all business stakeholders that would use the application.  This got me initial buy-in of all stakeholders, and then we took the lean ux practices that supported that vision and used only those.  I used most of what I listed, was ready to do all, but just what would get the win.  As an example, I expected to develop full user personas, but it ended up that wasn't needed in that environment.  But wireframing and UX reviews were extemely important, and we built things initially in powerpoint, but as the project evolved, this advanced into using other tools that are much closer to code, such as basalmiq and sketchflow.

  • Joel Tosi
    By Joel Tosi  ~  3 years ago
    reply Reply

    Hi Michael,

       A 90 minute talk is rough.  Could you do anything to make this more interactive?  Are there any exercises you could build upon?

    Best,

    Joel

    • Michael Heydt
      By Michael Heydt  ~  3 years ago
      reply Reply

      Thanks for the input Joel.  I was debating if this would be 45 or 90.  45 goes quick, and 90 tend to be long (I was thinking 60 would be perfect - but it was not an option).  At the start of the proposal I was at 45 minutes, then switched to 90 at the end, as I thought of earlier versions I've done that I know i could have go longer.

      So, at this point I changed the proposal to be a 45 minute talk.  I may have to be real efficient at that time and maybe trim a couple of items, but that's good as it's better for the audience.

      • Joel Tosi
        By Joel Tosi  ~  3 years ago
        reply Reply

        Thanks Michael, I do think that would be a better experience.  What material do you think you would trim?  Could you update the description accordingly if you don't mind

         

        Best,

        Joel

        • Michael Heydt
          By Michael Heydt  ~  3 years ago
          reply Reply

          I can do that over the weekend.  I wanted to get this in before the deadline, and I can work on the refinement now.

           

          And thanks again.

          • Michael Heydt
            By Michael Heydt  ~  3 years ago
            reply Reply

            I looked at revising the description a few time, and I think I like it as-is, and don't think I need to trim it.  


  • Johannes Brodwall
    Johannes Brodwall
    Niruka Ruhunage
    Niruka Ruhunage
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Beginner

    Can you maintain agile engineering practices with a distributed team?

    Johannes is the Oslo based Chief Scientist for the Sri Lanka based company Exilesoft. In order to promote agile engineering practices, he uses remote pair programming to connect with teams halfway across the world.

    In this talk, we will go through a practical approach for remote pair programming adopted for high-latency situations. We will demonstrate remote pair programming with a live example and we will discuss the advantages and usages of the approach. We will also cover the practical parts of remote pair programming, such as tools and setup.

    After seeing this talk, the audience should be able to remotely pair with members of their distributed team. They will also get a lot of tips on how to use pair programming effectively in both local and remote settings.

  • Liked Andrea Heck
    keyboard_arrow_down

    Distributed Product Owner Team for an Agile Medical Development

    Andrea Heck
    Andrea Heck
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Advanced

    We are developing medical imaging and workflow software in an agile way with development teams distributed to several countries. One of the major challenges is how to set up and communicate within the Product Owner team. There we have to deal with the distribution, e.g., have the Product Owner either onsite with her peers or with her Scrum team, travelling, or with proxy. We need people who are good in two different fields of knowledge: medical and software development. As a third issues, the environment of the customers may be different in different countries.

    We have ramped up local Product Owners in different countries, have found local collaboration customers, and have developed a set of communication channels and workshops how to synchronize Product Owners in the team, share a common vision and backlog with their Scrum teams, and collaborate with customers locally and globally.

  • Liked Naresh Jain
    keyboard_arrow_down

    SAMPLE PROPOSAL - Product Discovery Workshop

    Naresh Jain
    Naresh Jain
    schedule 3 years ago
    Sold Out!
    90 mins
    Tutorial
    Beginner

    Many product companies struggle with a big challenge: how to identify a Minimal Viable Product that will let them quickly validate their product hypothesis?

    Teams that share the product vision and agree on priorities for features are able to move faster and more effectively.

    During this workshop, we’ll take a hypothetical product and coach you on how to effectively come up with an evolutionary roadmap for your product.

    This 90 mins workshop teaches you how to collaborate on the vision of the product and create a Product Backlog, a User Story map and a pragmatic Release Plan.

    This is a sample proposal to demonstrate how your proposal can look on this submission system.

  • Liked Karthik Sirasanagandla
    keyboard_arrow_down

    When Agile becomes Fr-agile..learn your lessons the fun way!

    Karthik Sirasanagandla
    Karthik Sirasanagandla
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate
    So you have heard of "Code Smells". Did you hear of "Agile Smells"? Yes or No; then this session is for you (us).
     
    In this session, Karthik intends to talk about the very many things that go wrong in companies that attempt to be or become Agile.
    But fault-finding is the easiest thing. Can Karthik provide concrete solutions? Yepp, he intends to share the solutions as well for most if not all the problems.
    And in same breadth seeks to know what others has to offer from their experience.
     
    Piquing your interest? Are you wanting to get a taste of some of the Agile smells? Below are some of them:
    * Belated Stand-ups
    * Non-participative stand-ups
    * War-zone Retrospectives 
    * Unfruitful Sprint planning meeting
    * Zero-Test development
    * Inverted Test Pyramid development
    * Gate-keeper QAs
    * Hierarchical Roles
    * Velocity Driven Development
     
  • Liked Savita Pahuja
    keyboard_arrow_down

    Battlefield Agility

    Savita Pahuja
    Savita Pahuja
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    Battlefield Agility® is a quest to make our deliveries better, more collaborative, faster and effective. It relies on age old principle from the Army to provide a holistic view of the problem landscape which a project team needs to solve and be able to succeed in this, through small collaborative groups working in coordination to achieve the bigger goals.

    Battlefield Agility® derives from the Agile manifesto and principles and adds to it the key ingredient of individual wisdom to create a plan for a team which will help it succeed in successful deliveries . This is a goal based approach to increase MVP and ROI.

    The purpose of this method is to make team members more focused about their work, equal distribution of work in the team and increase productivity.

    Battlefield Agility enumerates the mechanisms of planning, better field view to all team members, ease of multitasking, reduce task switching.

    Key benefits of Battlefield Agility® 

    • A focused approach to software development as development proceeds through small battles to be won
    • Reduced multitasking and better efficiency of team members
    • Faster deliveries as the work is divided to right sized battles to be won
    • Parallel efforts by team members ensure the time to market is significantly lesser
    • Less process overhead as the collaboration is real time and more time is spent on the ground than on meetings
    • Small teams ensure close camaraderie and collaboration among team member
    • The team can even work on disparate work areas ( if required) in order to make best us of their expertise

     

  • Liked Tania van Wyk de Vries
    keyboard_arrow_down

    Agile metrix: How do you measure the success of your agile implementation?

    Tania van Wyk de Vries
    Tania van Wyk de Vries
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Advanced

    Humans are creatures of habit and agile is really challenging that part of our existence everyday. I have seen many teams thinking they now get agile and they take what they learned and just practice it everyday without really reflecting on where they are at or the fact that they are not really moving forward. So in order to say your teams and organisation are really becoming more and more agile everyday you need some metrix to measure against.

     

    The collection of the metrix are 2 fold:

    1. Metrix are tracked through the agile project management tools teams use. We have defined the below set of metrix to interrogate our data to tell us how we doing.
    2. Some of the metrixs are done by getting feedback from teams and clients through surveys.

     

    Some of the metrix include:

    1. Measurement of quality
    2. Measuring customer satisfaction
    3. Measuring team happiness
    4. Measuring continuous improvement in process and technical practices
    5. Measuring time to market
    6. Measuring ROI
    7. Measuring productivity
    8. Measuring overall project progress
    9. Measuring change and improvement

     

  • Liked Vibhu Srinivasan
    keyboard_arrow_down

    Coding with Geeks- De Code the secrets behind TDD, BDD and ATDD

    Vibhu Srinivasan
    Vibhu Srinivasan
    schedule 3 years ago
    Sold Out!
    90 mins
    Tutorial
    Intermediate

    This session is a coding sessiont that takes a problem and shows clearly what is the difference between TDD, ATDD and BDD. Ths session uses code for the server layer as well as UI layer.

    This session is not for you if you do not code. If you do code, please bring your laptop as we delve into the details of all these styles of programming techniques.

    We will rotate between ATTD, TDD and BDD periodically and show it at use in different layers. This session will be using Java , Rails, Scala and C# together so that you can see how you can benefit do these techniques even when coding in different languages.

    We look at common pitfalls and wrong beliefs that programmers have when it comes to these concepts

    This session is purely keyboard and you will have to bring a laptop.