Saturday Reading

Hypothesis-driven development

Hypothesis-driven Development (HDD) is a methodology that helps us avoid this gamble and approach product development with more certainty.

First, form a hypothesis. For example, “releasing feature x will lift signups by 2x,” or “patching bug y will increase daily actives by 5%.” Now, challenge the assumptions of your hypothesis. For example, the hypothesis “moving the submit button above the fold will increase form submissions” makes an assumption that people aren’t submitting the form because they aren’t seeing the submit button. But what if you knew that everyone that saw that form did scroll down and did see the submit button? That insight would invalidate your initial hypothesis, saving you a bunch of time and energy!

Designing UX Login Form and Process

Nice examples from Twitter

  • Takeaway: Rather than providing a ‘Login’ or ‘Sign in’ buttons, it’s better to show the input fields, so users can login.
  • Don’t Use ‘Sign In’ and ‘Sign Up’ Together
  • Differentiate Login from Registration
  • Allow User to Log in Via Facebook, Twitter or Google +
  • Let Users See Their Password (Users make more errors when they can’t see what they’re typing)
  • Use Email Address or Phone number as a Login (not username)
  • Keep Users Signed In When They Register
  • Warn Users That Caps Lock is ON (Desktops-only)
  • Auto-focus The First Input Field (Desktops-only)

Product Managers should growth hack.

  • The idea behind viral loops is that a company will have a core loop that is repeated so many times over different generations of users that it causes a tailspin out into unfathomable popularity i.e., becomes the thing that all the kids are talking about.
  • PM’s should be focused on engineering growth drivers in to the product just as much as features.
  • Growth isn’t an afterthought, and I agree with your thesis that PMs should be thinking about building growth into the business from day one. Understanding which loop to use (the viral loop is one; there are others) is a key product architecture decision before you write the first line of code.

Jason Fried’s 13 unconventional rules for getting clients

  • Sell your service like a product by removing the barriers and unknowns about what you’re selling.
  • Make your portfolio about ideas not pretty pictures of your work.
  • Write and sell with short 1-page proposals.
  • Don’t work with bad clients.
  • Hire your clients.
Like what you read? Give Adeem Maqsood Basraa a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.