Return every registered user's ID, name, and current subscription plan

The shape

FROM users reads the full Streamhub user base, and the three columns in the SELECT list shape every row into the slice the growth team needs to look at tier distribution: who the user is and which plan they're on.

Clause by clause

• SELECT id, name, plan returns three columns per row, in source order. The identifier comes first so individual users can be cross-referenced if the growth team wants to drill into a specific account; the name makes the result human-readable; the plan is the column the pricing-strategy meeting actually cares about.
• FROM users is the row source — the table of every registered Streamhub user. There's no WHERE clause, so every registered user comes back, which is the right grain for a distribution analysis: you can't see how the tiers split if some users are missing from the result. The shape recurs across SaaS tables. Whether the data is users, products, accounts, or events, the pattern is the same — name the table in FROM, name the columns in SELECT, and let the result land at the grain of one row per record.

Why this and not SELECT *

The users table likely carries more columns than these three — email addresses, signup timestamps, billing references. None of those belong in a tier-distribution analysis; they'd just make the result wider without making it more useful. Returning the three columns the growth team needs keeps the dataset focused on the question being asked. A SELECT * query would also pull personally identifying fields like email addresses into a meeting deck that doesn't need them, which is the kind of unnecessary exposure tight column lists quietly prevent.