Pyramid in Louvre courtyard.

No rules, No schools: Time to learn

Old-model societies, dreams of the ’50s, were built on concrete social structures bolstered by strictly-defined social relationships. Our elders presumed primitive stereotypes and implemented a mechanistic vision of community: The cop, the addict, the car salesman, the wetback, the teacher, the clerk, the JD, the housewife, the jock.

This old model is crumbling in the face of new technologies and escalating pressures from a fragile environment and scant resources. Our parents’ compromises are not ours. Unable to train for a secure social position, we face demands to re-invent ourselves and our social relationships on a daily basis to fill the shifting needs of communities in crisis.

First, this means that learning is not boxed up into times or processes – learning is life-long and boundless.

Second, it means that collaborative, grass-roots efforts have an advantage over the rear-guard actions of embedded privilege – we are more agile, more resourceful, less comfortable. Oh, and brutally honest.

Opportunity in community

How does one accumulate skills and knowledge in a dynamic society? Through immersion in impromptu communities of subject experts, tech-wonks, artists and other assorted life-long learners.

Within these communities, skills are developed, invented and refined by direct, personal engagement using a 5-step, pro-active process:

Picture it. Visualise the action steps and skill-sets required to reach objectives.

Do it. Step by step, without flinching, without shame, using the talents, skills and resources at hand. However you can.

Evaluate it. In community, to improve individual skill and expand the group repertoire, evaluate accomplishments, failures, investments, opportunities seized and missed. Re-assess objectives, raise benchmarks, discover ways to better use talents and other resources.

Fix it. Do it over, with knowledge gained. Get closer to your objectives – efficiently, effectively, reliably.

Teach it to someone else. What you learned. So they can refine and apply it. You learn by doing; you learn more by teaching. Both individuals and the community build, through sharing, necessary skills and insight.

What dynamic learning looks like

Learning structures draw on the community skill and talent. Teams of learners and supporters collaborate to build useful skills and gain knowledge around a dynamic, open framework.

The Framework is assembled by experts in learning and community development. A Learning COR begins with a defined skill foundation and charts a path to the accomplishment of learner-defined objectives in a general field of endeavour.

Experienced practitioners provide a sounding-board to help each learner Focus personal talents, with efficiency and effect, toward the achievement of objectives. This mentoring approach takes on each challenge from complementary viewpoints: Limitless-opportunity and Been-there-done-that.

Technical rescue teams provide First-Aid to keep trivial processes and procedures from becoming learning roadblocks. As near-peers, these teams also challenge learners to take risks and trust their instincts.

Feedback from learners, tech teams and practitioners enables the program to continually re-invent itself, retain relevance and gain in power. The tree of learning keeps growing.

Companies where I work generally have a fundamental need to make learning a profit generator. Which is why they can hire me. The stability of a profitalised corporation helps keep continuity and authenticate outcomes. The volatility and responsiveness of more anarchic community operations keeps the work alive and relevant – as long as common energy is sufficient to sustain a quality effort.

In both scenarios, the enabling product is a Learning COR, the framework that structures, guides and rewards the learner throughout a project. I’ll talk about that in my next article.

Meanwhile, I’d love to hear from y’all about your learning and teaching experiences, good and bad, and what those have led you to value in the learning process.

My first In-the-browser design

Thank you Robert Nealan

Check out http://originalvincie.com/. It’s an Agile project, so ongoing, but even in its nascent form celebrates personal firsts:

First use of Robert Nealan’s Design in the Browser.

Robert was the second design person to make me believe I could get on top of the coding mysteries and make my pages do what I want. I have some questions for him – in that first workshop he gave, we didn’t get beyond beginning steps – but it has been exciting to move from closed systems into something portable.

First one-page site.

I didn’t understand why folks made one-pagers. Or, rather, I understood the concept but the reality seldom seemed interesting in an experiential way. Generally, soft on content. But for this client, I realised that I wanted a full rollout of the product, in a way that phone users could enjoy, with no decisions and no clicks until you get to answering, Which of these do I want to buy? question.

And, yes, I know it’s got an Info page to come, which makes it a two-page site. But it works on the one-page concept: Scroll not click. Draw them in.

First Agile project.

Working with a diverse team, with everyone up to their eyeballs in every aspect of UiX, branding, product lineup, imagery, pricing, messaging – if we waited until everyone agreed, the brand would never launch. Not to mention that most of the team can’t picture things they can’t see and use, so we need this for, if nothing more, a test site.

I think it works. Do you?

There are questions, of course. And things that need doing:

The Info page, another one-page model, needs drafting.

Real photos need to be shot, showing the product as the branding and marketing gurus want them.

Photos need to be optimised for web, so they pop up instead of lazily scrolling onto the page.

Type faces and design details need crafting. For this first go-round, I stuck with generic. Next, I need to tackle mixin files and learn how to Grunt. I’ll be asking Robert questions.

Let me know what you think about the page, how it looks and how it works. Ask questions about how I did it and why. Give me ideas on ways to make it better. Ask me out for coffee. http://pdquin.com/contact/pdq.php