{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidf6hy6rb74mrudzemnh4pnumjldrpwclwilfsxi6ldmze67a4kwu",
    "uri": "at://did:plc:c4uo5im4kb23i76qndr43xi2/app.bsky.feed.post/3mjfhkbkfhwh2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreickgxuzzzx7bzdb2omjzsyq7fdi3a57tczbdik7nhb63zv3wfmoce"
    },
    "mimeType": "image/webp",
    "size": 297988
  },
  "path": "/links/is-this-really-needed",
  "publishedAt": "2026-04-13T04:00:00.000Z",
  "site": "https://jonathanstephens.us",
  "tags": [
    "Product Design",
    "Design",
    "Removing",
    "Necessities",
    "Form Follows Function",
    "Principle"
  ],
  "textContent": "> When you strip a flow down to its essentials, the signal you get back is so much cleaner. If users drop off a three-step onboarding, you know exactly where and why, but if they drop off a twelve-step one, good luck trying to isolate the friction.\n>\n> Every element on screen competes for attention and the more choices you present, the harder each one becomes for the person who has to make it.\n>\n> Fewer options don't limit the user, they clarify the path. A single call-to-action on an empty page is unmistakable, and a form with three fields feels respectful of someone's time. Reduction gives users confidence in what’s actually there.",
  "title": "Is this really needed?"
}