Comment Re:Contribute how? (Score 1) 149
First of all, establish exactly what it is they are asking you for. 'Strategy' has to be one of the most abused words in the modern world. Is it really strategy - ie setting goals without defining how they are acheived? Is it policy - ie setting the framework of rules to work within while achieving the strategy? Or is it tactical advice - the nuts and bolts of how you actually implement the strategy and policy?
Assuming it is strategy, then
Second, define what you want IT to achieve - in terms of benefits and abilities, and what you want IT not to do - in terms of drawbacks and liabilities.
Third - prioritise the importance of each of the individual results from point two above.
Now you have a list of things you want IT to do, and you understand how to allocate funds and time, based on their priority. The next steps are to decide the policy to run them, and tactical implementation.
You'll get a lot of folks here saying things like "allow FOSS...deny " These aren't direct strategies. A strategy would be to allow solutions to be developed/deployed based on fitness for purpose. The conseqent policy would be to allow multiple OS / applications to be deployed within a controlled framework. The following tactic would be to assess what the user needs and can afford, identify what potential market solutions are out there and how much they cost (capex and opex) and pick the best.