Infrastructure: bigger and faster may be desirable - but doesn't automatically means better. Choose bandwidth and equipment to serve your needs.

Access: don't expect people to come just because you provide computers and open the doors. New users need help.... public access isn't the same as supported community access. Lack of confidence, literacy, disabilities are only some of the barriers to use - meet people and find out their needs. Take computers to people.

User support: users need help to do the things they want to do - not just technical assistance. New users often need reassurance they won't 'break' a computer - but they also need to make their own mistakes.

Community applications: information is useful - but community grids are more than a web site. Look at the many successful community uses of the Internet. Encourage local organisations to build Internet use into their work - not just see it as an add-on.

The spark: the initiative to start a community grid is as likely to come from an individual as an institution.

Leadership: look for champions for different aspects of the community grid - technical, content, community involvement. Recruit some people with 'clout'.

Planning: don't just leave it to the techies. Ask the 'why' questions before jumping to the technical 'how'. At the start, carry out an audit of the resources you have already.

Partnerships building: it takes time to build partnership working. Technology doesn't overcome age-old human problems of collaboration.

Community involvement: run demonstrations, but avoid complex wiring diagrams. Start with people's interests and needs - not flashy solutions

Structure and systems: there are no off-the-shelf models - but we can look at the range of activities managers will have to undertake and learn lessons from elsewhere.