When you’re a more experienced Salesforce consultant, one of your usual tasks is to help write user stories. Typically, the consultant writes the functional part of the story, while the business analyst fills in the rest.
The question then becomes, how much detail should you add to the user story?
If you add a ton of detail, and explain the exact build steps, then the junior consultant doesn’t have anything thinking to do. If they are not thinking, they are not learning. They are like code monkeys, blinding typing your instructions with the keyboard. And their job satisfaction will probably go down.
If you add insufficient details, the consultant will need to ask you follow-up questions. They need more guidance, and will keep bothering you until the level of detail is adequate. I’m sure you have better things to do and don’t want to be pestered.
So the balance is somewhere in the middle. Sufficient detail so they clearly understand what they are supposed to do, but not overly detailed so they don’t learn. Ideally, you want the card to push them slightly past their comfort zone.
The takeaway
Passing your comfort zone is a wonderful place to learn. Write your user stories so that the people doing the work understand the business context and overall technical direction, then let them figure out how to do it.