AK+Toolkit

Starting at the end…

I envision a website that has a landing page which is colorful, professional, and easy to navigate. The main page would have a title and a brief description of how the site can be used. Below the description could be three buttons labeled three simple words to indicate levels of tech ability – beginning, intermediate, and expert. We could also put brief statements next to the buttons describing a user that would fall into this category. Each button would launch another page. Also from this homepage, there could be buttons that link to an about page and a feedback page to allow for people to learn more about the background and to help improve the site.

When users navigate to the next page, there should be a way to search for information. Maybe drop down buttons to find the standard, or drop downs to find the grade level. Based on feedback, we need to provide lesson ideas that are associated with the tech. This needs to be incorporated into the search. Every single page should be easy and clean like this. We can flow chart this later. I think that no matter which button they click it should take them to 2 choices for points of entry. 1. I want to choose some standards and start there, or 2. I want to learn about some new tools and start from there.If they choose 1, then depending on their level, it would offer lesson ideas, then drill down further to a some suggestions for specific tech (including what equipment, apps, software, connectivity, etc) would be needed, and tutorials. If they chose 2, it would go straight to tool options by category (embedded presentations, embedded video, content specific interactives, content specific activities etc), but then continue to offer standards as a side option for entry.

I think we also need to make sure we are constantly defining what we mean by these levels. I wouldn't think a novice would link to access for student blogs, websites, or embedded media, but I think an Intermediate might be introduced to these things. With Advanced I think we could assume some knowledge with these types of things. Anyhow, I think maybe we should come up with some definitions of what these categories mean and what types of skills they include, and maybe even post it or have some kind of a survey people could take to get a clearer idea of what that means as far as their own skills.

I LOVE this! It's like you are reading my mind!

How do we get there? **Before step 1. I forgot to put in the big matzo ball - the data (the standards). I think step one is going back to the standards and building a "pre-database." We are going to need to list each standard in preparation for the database. That means each standard will need tech associated with it. Each standard will need three levels of tech. Each standard will need a grade level.Each standard will (eventually) need lesson plan ideas. All this in anticipation of building something searchable. Although Excel is not the eventual program, it might be a good tool to use to start building the data. What do you think?

1. We need a website that is maintained somewhere. ASTE? This can be done with no problem with a link - we will always have to take responsibility for maintaining it. It would be nice if ASDN and even Dept of Ed had our link! Also, would be good to lobby individual districts to include it on their district websites.

2. We need a database tool that can be housed somewhere. ASTE again? It would need to be a server that stays on all the time and can handle increasing traffic. Again - if we handle all of that, ASTE just needs the link - no problem. I see the database aspect as our last step. Of course we'll have to keep that structure in mind as we plan, but I think it's something we can find (obviously with some outside help) if we just have all the "stuff".

According to several forums Access and MYSQL come up quite a bit as easy to use. Both cost. There is a free database tool called OpenOffice, but I’m skeptical of this.

3. We need to design the initial landing page and the pages that link from there. We need the first landing page, a page for about to showcase our purpose and maybe some of our research findings, a page where people can give feedback, and pages for each level of tech skill to search from. I would like to see the feedback page be like a comments page where the comments are open and viewable by all. Of course, the owners would have editing rights to dump spam and inappropriate entries. I like the type of page you have mocked up here as a landing page. Maybe some links at the top like "about" and "research", but if we crowd up the landing page with that we will start to lose traffic I think. It should be visually easy from the very first click.

4. A LONG time ago, I helped build a database with Access. That part of my brain is rusty. I think we are going to need some help. Definitely. I know how databases are supposed to work, but my last experience actually building one goes back to Microsoft Works...so that says a lot (or a little) about where I'm at with that. Definitely will need help. Weird thing is, there are already companies out there that exist for this purpose. I had this exact issue a few years ago when we were working on curriculum. I wanted a searchable database that showed our curriculum as aligned with standards and resources that teachers could easily choose from as they were building lesson plans. We kept doing curriculum work each year with this goal in mind. Finally about 3 years ago a company came out of the woodwork with a cold call offering exactly this. It's still very much a work in progress as we have to work together constantly to make sure things are aligned and working, new resources get put in and are searchable, and it can accommodate changing texts, curriculum, and standards (It's a mess right now with new standards), but we are getting there.

5. Once the database is set and the pages are built, we will need to solicit feedback. I think we can put a BETA version out while we are in the initial feedback stage. Yes

6. Then it is a matter of maintaining the page and keeping links updated along with new findings. We'll get rich from this so no problem - we'll just hire some secretaries and programmers. :)

Ok I've thrown in my 2 cents on your work and it really feels like we are thinking alike on this. Let me tell you a little bit about what I'll be doing next semester at work because I'm trying to approach this in a way that also works with our project:

First of all, I'm attacking the NAS standard by standard. For each one coming up with ideas for classroom examples, sample lesson plans, and resources we have that align (texts, etc.). This is also an alignment process as well, so I'm parsing through our current curricular objectives and seeing which ones most closely align with each standard, and hopefully getting a clearer idea of which ones can GO. Our curriculum is cumbersome and huge, to the point where it's really not possible for a teacher to accomplish it. That, in my mind, makes it completely unusable.

When I'm done, I'm hoping for a couple of things - 1. that I'll see a way to "blow up" each standard and extend it to something where the focus is more problem/project based, less emphasis on "testable", just because I think that's a crappy way to teach, and since I'm the architect of this project it's going to have my stamp all over it.

2. to try to make these standards/our curriculum something that lends itself to portfolio building. I see student portfolios as a key component in our teacher eval system. If test scores have to be a part of that so be it, but if we can choose the rest, I want it to be digital student portfolios. In order to sell that idea to the rest of the eval committee, I have to make sure that it's do-able and not overly cumbersome for evaluators. So I want something built into each standard that lends itself to that.

3. To do exactly what we're doing with the tech-specific standards, but also to bring tech suggestions into non-tech specific standards where ever possible. Which I think you and I also want to do anyway - I think for the purposes of our Toolkit it makes sense to focus on tech-specific standards first, but would be far more complete if we could incorporate every standard eventually.

I intend to use some of the frameworks we've already used/talked about here - the Tech Integration Matrix, TPACK, and of course UbD.There will be lots of cornerstone assessments built in. The Danielson Model will be the over-riding umbrella for the whole thing - but that's more of a reference point.

So now you can see where our stuff ties in soooo very nicely to my work!

LEVELS OF KNOWLEDGE/SKILLS Familiarity with programming applications such as Scratch, Microworlds, GameSalad ||
 * ||  || Novice || Intermediate || Advanced ||
 * || Skills ||  ||   || video, screencasting, embedding ||
 * || Knowledge ||  ||   || Understanding of seamless integration into daily tasks/projects ||
 * || Applications ||  || Class website, blog or wiki || Students blogs, websites, or wikis