Sometimes, that's fine. After all, I would assume no rational human is going to "command" someone to do a thing if they don't think they want that thing done. Personally, I've found that pointing people in a general direction ends up yielding far superior results. Empower your team, and they'll surprise you, usually in a good way.
Sometimes your team will surprise you but often they’ll horribly disappoint you. If the stakes are low, sure do whatever, but if shit matters …
Long term, if you have the right team, the positive surprises will more than cancel out the disappointments and the "meh" results. But, if it's a life or death type matter, fuck the long term -- you have to survive the short term before you start worrying about that. You can't manage or lead an organization that's at war the same way you would one that's at peace, and nor should you try.
Worst are the people who both don’t like the “I need you to …” task giving and do absolutely nothing when left alone or only given a goal and a direction. How do you deal with it if you are working on an industry where performance adjustments and feedback can take years and you can coast without doing anything four more than a couple of years?
The bad engineering managers I've seen seem to suffer from anthropophobia when they aren't giving orders in a meeting room.
But I think your suggestions mirror my experience in actually getting the person to do the thing. The other benefit is that the same steps, more or less, work well when managing up as well as down.