The heuristics content is good; I like the assignment (looking for examples in pairs). I'm not 100% sold on giving examples that aren't in the tech space (e.g a stove top). As an apprentice, I'd want more signposting than that (though everyone is different I guess). Small thing as well: we haven't actually said what the Heuristics are?
Composition
This has the makings of a really good lesson, but I'm not sold on the CSS side of things. We've introduced some key topics (white space, typography, colors) and it makes more sense for me for the apprentices to find good/bad examples of all this in the wild then to turn their attention to designing their app in terms of the topics mentioned. Perhaps CSS can feature but in a more subtle way, e.g. what breakpoints/devices do you need to cater for?
A nice outcome from this lesson is that they take all the concepts and make decisions on font, sizes, color palette etc as a group. Ideally the coach should be able to quiz them on colors, margins, units of measure etc and they will have answers after this lesson
Prototyping
Again, I think this has the makings of a good lesson. I like the way we're starting with sketches and building up.
I think we might need to offer up some tools to do create wireframes/high fidelity
I think I'd be more concrete about the sketch assignment as this could lead to some really good discussions (i.e. actually set it as an assignment midway)
Are we capturing the iterative nature of Agile design? Do we need to bake this in more?
The tone of voice is different - you're using "I" whereas we haven't before. E.G "With the high fidelity mockups I can really communicate my idea clearly to stakeholders and other members of the team." I'd propose we change to "we" or "you"
Some initial feedback:
Heuristics
The heuristics content is good; I like the assignment (looking for examples in pairs). I'm not 100% sold on giving examples that aren't in the tech space (e.g a stove top). As an apprentice, I'd want more signposting than that (though everyone is different I guess). Small thing as well: we haven't actually said what the Heuristics are?
Composition
This has the makings of a really good lesson, but I'm not sold on the CSS side of things. We've introduced some key topics (white space, typography, colors) and it makes more sense for me for the apprentices to find good/bad examples of all this in the wild then to turn their attention to designing their app in terms of the topics mentioned. Perhaps CSS can feature but in a more subtle way, e.g. what breakpoints/devices do you need to cater for?
A nice outcome from this lesson is that they take all the concepts and make decisions on font, sizes, color palette etc as a group. Ideally the coach should be able to quiz them on colors, margins, units of measure etc and they will have answers after this lesson
Prototyping
Again, I think this has the makings of a good lesson. I like the way we're starting with sketches and building up.
I think we might need to offer up some tools to do create wireframes/high fidelity
I think I'd be more concrete about the sketch assignment as this could lead to some really good discussions (i.e. actually set it as an assignment midway)
Are we capturing the iterative nature of Agile design? Do we need to bake this in more?
The tone of voice is different - you're using "I" whereas we haven't before. E.G "With the high fidelity mockups I can really communicate my idea clearly to stakeholders and other members of the team." I'd propose we change to "we" or "you"