• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Finally, you can manage your Google Docs, uploads, and email attachments (plus Dropbox and Slack files) in one convenient place. Claim a free account, and in less than 2 minutes, Dokkio (from the makers of PBworks) can automatically organize your content for you.


Technology projects

Page history last edited by Jacob Martin 5 years, 10 months ago



Wiki - Steps  Pathways  Forum  Other Projects  Mentoring





A technology project solves a problem. You get to create or design something to help people or make life easier. There are many different steps you could do for a technology project. The steps here are designed so you can enter as many competitions as possible.




You need to start with a problem or a need. The whole idea of technology is improvement.  You can start with a problem that many have tried to solve before and you can come up with ways of solving it better.




You can then write your aim -this states what you are going to do. For example “I want to solve the problem of not being able to get a tent into its bag”. 




This is when you define what set of requirements your project needs to reach to be successful - for example - it must be safe (what parts need to be safe?) strong (does it have to last a long time?)..etc




Design your solution


This is where you start to think about how you are going to be able to solve your problem.




These are just rough sketches in your logbook that are your first ideas. Put as many designs down as you can think of even if they seem no good, because a lot of good designs are a combinations of a lot of concepts.




You can now start to refine your designs and start changing things.  Make sure you keep in mind the problem you want to solve. You can do most of the work in your logbook or you can do it on large sheets of paper. It’s a good idea to use colour as well. But modifications are never over with a technology project and as you come across problems, you will need to change and modify your design.




Do a list of all the materials and tools you will need - you may have to ask to borrow some from school. Don’t be afraid to ask, companies are more than happy to give you stuff you need for your project.


For examples go here



Build a mock-up


The best advice for designing a solution to a problem is to do a mock-up of your solution. It could be a cardboard cut out or a rough wood model  - this will sort out any problem before you build the real thing.


Doesn’t have to be finished


It is great if you can have it working but you don’t need to build the final solution - you can build what’s called a prototype, which just demonstrates what the final model will look or work like.


Getting help


Don’t feel like you’re alone - you can get as much help as you want as long as you do the work. School is a great place to start; ask if you can use the workshop during lunch or the computer labs. If you can’t afford materials, ask around town - businesses are always keen to give you materials if you say it is for a technology project and that you will acknowledge them.


Test it


You may think that a technology project doesn’t need to be tested, it just needs to work, which is sort of true. If you want as much as you can get from your project, you will find out how well it works or solves the problem.  You could do this by comparing it against something else or you could do a questionnaire and get people to comment on how they like your solution. Either is enough for your project to be able to get to the next level.




Collect your data


You will need to collect all your data from your tests or questionnaire - put it straight onto the computer on a table. Then you can put it onto a graph so that people can see it quickly and easily.




  • Write down a summary of your test or questionnaire results.

  • How well did you meet the brief?

  • What would you do differently next time?

  • What uses does it have?

  • What are your future plans?

Comments (0)

You don't have permission to comment on this page.