Skip to main content

How do you connect with Digital Natives?

I'm thinking a lot these days about the environment that we inhabit.  And who is here beside me.  The faces look similar to when I started in this business 20+ years ago, but what makes those people tick, is quite another matter.

Many of these faces belong to Digital Natives - a person that grew up in a digital world.

The term “digital native” and “digital immigrants” comes from Marc Prensky a writer, speaker, consultant and inventor in educational games and learning processes. In coining these terms Mr. Prensky is drawing on the analogy of natives to a homeland and in this case we are talking about the digital land or those who have always known the internet and the immigrants are the ones that are coming to this new land, some kicking and sreaming and others eagerly exploring and learning the new skills, language, and culture needed to travel in this digital world (Prensky, 2001). In this new digital land the natives have an advantage over the immigrants. This advantage stems from the immigrants lack of cultural context with which to judge, and perceive experiences, while the natives grew up in the new land and have assimilated to the environment. The natives have subtle differences in speech, social interactions, and are fluent in the digital communication forms that are prevalent in the new land, whereas the immigrants are perceived as having an accent. This accent “can be seen in such things as turning to the Internet for information as secondary source rather than their first source, or they will want to read the manual for a new program rather than assuming that the program itself will teach them to use it” (Prensky, 2001). Digital natives will be confortable using neologisms. A digital native will be so familiar with the Wikipedia that they will be comfortable with the word used as a verb. A digital immigrant on the other hand may well ask what is a Wikipedia? Wikipedia is an online multilingual, encyclopedia project, which has been created by a collaborative effort of hundreds of thousands of volunteer contributors. For example one may hear a digital native say, “Just a minute, while I wiki that”. The native is implying that they will search for the topic of conversation on the Wikipedia web site, and then include information found into the conversation. What may surprise the digital immigrant is that this referencing the web site and searching for information will happen in parallel with the continuing conversation, perhaps with very little interruption of the conversation. This ability to multitask a conversation with individuals (verbal communication) and a conversation with a web site (textual communication); perhaps over a mobile device with a screen and keyboard that fit within the palm of your hand, is one characteristic of the digital native. The Digital natives are accustomed to rapid change, and perhaps even thrive within this environment. The immigrant on the other hand may cling to stagnant eddies in the flow of innovations. Innovation that may appear to the immigrant as high-tech, such as email, but be perceived by the digital native as old and tired.


Excerpted from: The Digital Generation - Teaching to a Population That Speaks an Entirely New Language by David Koontz; Tracy Gibson, Ed.D.; & Mark Van Den Hende, Ph.D.





Did You Know  - from the wiki Did You Know?/Shift Happens


Here's a great article and example of engaging the Digital Natives in education.  Wake Forest University's Business school gave newly enrolling grad students iPods - just so they could connect with them via video.

Video Production for WFU’s Summer Management Program



"Web-based video is quickly becoming a must-have to tell your story."
-- David Caudle

These guy's at Frogman taught me that do really connect one has to immerse themselves - to dive deep. I used that metaphor in a training class just this week. We were creating a product scorecard - comparing features of an existing application to desired features of a product to be developed. The scorecard has to allow for the reader (the user) to dive deep into the information and right down to the data layer if they so choose.
Full disclosure:  Frogman Interactive is my brother's web development company.

Post a Comment

Most Popular on Agile Complexification Inverter

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?



Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…

Webinar: Collaboration at Scale: Defining Done, Ready, and NO.

I was invited to participate in a Scrum Alliance Webinar.  Maybe you would like to listen to us in a discussion of techniques to collaborate at scale (remotely and with many people).  The topic is one that I've got some experience in discussions - yet I never seem to get to done...
Collaboration at Scale: Defining Done and Ready and NO for Distributed Teams
With Joel Bancroft-Connors, Agile Organizational Coach; David A. Koontz, Agile Transition Guide; and Luke Hohmann, CEO and Founder of Conteneo, Inc.


14 February 2018 11 a.m. ET (USA).




The Scrum Guide is pretty clear on the criticality of the definition of Done: "When a Product Backlog item or an Increment is described as "Done," everyone must understand what "Done" means. However, the Scrum Guide ALSO says that the definition of Done can "vary significantly per Scrum Team." This leads us to examine when and how the definition of Done should vary, how distributed teams should cr…

A T-Shaped 21st Century Knowledge Worker

Knowledge workers in the 21st Century must have many areas of deep knowledge, while also be capable of collaboration across multiple other domains with dissimilar T-shaped individuals.  This description of a person is a metaphor.  Compare it to the shape of the "I" in the classic saying there is no "I" in Team.


I first read about Scott Ambler's term "Generalizing Specialist" - but it's so hard to remember the proper order of the words... get it backwards and it has an inverted meaning... T-Shaped is easier to remember. 
A generalizing specialist is someone who:
Has one or more technical specialties (e.g. Java programming, Project Management, Database Administration, ...). Has at least a general knowledge of software development. Has at least a general knowledge of the business domain in which they work. Actively seeks to gain new skills in both their existing specialties as well as in other areas, including both technical and domain areas.  General…

A FAILURE to Communicate

I was working with a failing team some time ago.  I use "failing" to describe the outcome of the team - not the people on the team.  Are you OK with that description?



An issue arrose in the stand up - a team member that was to verify the quality of a procedure did so and reported that there were a few records that didn't match expectation in the data set.  Upon inquire the number of records not matching was over 2000.  Most people acknowledged immediately the exaggeration - I could tell by the laughter.  After about 10 minutes of discussing the details of the problem - it appeared the team had a handle on the specific situation.

I stopped the discussion and inquired if they could name the impediment.  One team member did a great job of describing the impediment as a _communication gap_.  Wonderful - I could work with that - the problem had a name and it didn't include anyones Proper Name.

"If the problem has a first name; we are going to have a problem."

I&#…