A useful way to decide whether a signature belongs in onboarding is to treat each one as a hypothesis, not a default. Map the flow and label every request by who needs it, what risk it controls, and whether it can happen later. Then compare completion and drop-off immediately before and after each step, split by first-time vs returning users and by device. For low-risk steps, test moving the request until the user actually needs the feature; for high-risk ones, explain the reason in plain language before asking. Keep a short weekly review of completion, support tickets, and any fraud or compliance incidents so removing friction doesn’t quietly shift costs elsewhere.