Stribe to be Instantly More Social

stribe-logo Recently, I had the opportunity to interview Kamel Zeroual, CEO of Stribe — Gold prize winner at Le Web ‘09. We covered topics ranging from this Paris-based startup’s origins to where it is going and how it is planning to get there.

00_stribe_homepage

Some Background

The Stribe product is a freemium online service, seeking to provide the capability to instantly create a social network on any website, confronted by a diverse array of competition from the likes of Ning, Facebook, and Meebo. And, it all began shortly after the 20 Kilometers of Paris race where the Stribe team…

“… noticed that all the people were checking their time two days after the race without being able to share, discuss, and experience the benefits of the online relationship. At that time, we (the Stribe team) were sure that all websites held the (unrealized) potential for being a social network.”

02_stribe_panelFrom this Stribe was born, seeking to provide the average online user…

“…more social features, getting more relevant content from any stribed website…”

… the website owner…

“…a plug-and-play service for interaction tools and getting in touch in other websites on the same topic…”

… as well as the application developer…

“…ability to create specific features, to suit their needs, such as casual games, special surveys, and so on. And an API will soon be available.”

Startup, Growth & Revenue

Stribe’s current strategy goes beyond its freemium business model to monetization, driven by virtual goods, casual gaming, advertising, and the crafting of viral mechanisms to drive the product’s growth.

01_stribe_manageIn speaking to the realization of the long-term vision, and where Stribe would like to be in 3 years, Kamel provided the wonderfully framed insight that only a startup founder can — by responding (with a big grin)…

“Well, could you ask me this question in a couple of months?”

“Running a start-up means being able to listen, discover the pain of your customers and users. We are a lean startup … very agile … making the best moves as fast as we can.”

And, as far as tips for the aspiring entrepreneur seeking to follow in the footsteps of Stribe, and other exciting startups like them, Kamel has the following advice…

“While it’s my first company … I’ve learned many things in a couple years. My advice is to focus on customers and market feedback … to figure out the perfect value proposition, price, and service.”

All Wrapped Up

Stribe provides a broad suite of features and functionality that touches the many cornerstones of Modular Innovation, from the Shareability of content to Interoperability with Twitter, Facebook, and Gmail, facilitating relationships amongst and between websites and the users that frequent them.

Check them out — and share your thoughts, advice and experiences in the comments below.

Enjoy!

Jeremy Horn
The Product Guy

About these ads

Prevent Good Metrics From Going Bad

chris2010 Guest post by Chris Cummings of Product Management Meets Pop Culture.

"It’s not my fault!" Those four words underscore so many of the discussions (or, as I like to call them, blamestorms) that accompany product management.

A reasonable person might expect that to be less of an issue when we’re talking about metrics. After all, good metrics are:

  • Aligned with the business
  • Honest
  • Actionable
  • Measurable
  • Objective

Who could argue with a number that’s honestly calculated, from credible sources, without bias or subjectivity?

Turns out, many people. Especially if they’re on the wrong end of a good metric.

Metrics Affect People

Many discussions about metrics in product management do a great job of looking at things logically but remain silent on the consumption of those metrics or the behavioral reaction to those metrics.

We measure what we figure is important. And if your job is connected to a metric, and you want to look good at your job, then you want that important metric to look good, too. It’s human nature.

Avoiding The Misuse Of Metrics

As a Product Manager, we play a key role in how metrics are collected and conveyed. Here are three tips on how to avoid the misuse of metrics.

Use the right mix of metrics

Too many metrics can lead to analysis paralysis. Too few metrics and you can end up really fine-tuning one particular aspect of your product (the part being measured) at the expense of something critical that’s not being measured.

For example, in online games, there are many things that could be measured (visitors, time spent, etc.) but the most critical metrics generally relate to viral growth (retention and referral) and total sales (revenue per user per day).

The goal is to determine the right mix of metrics to provide an insightful, actionable, balanced view of your product. Measuring in this way amounts to leadership, and encourages others to think about the product holistically as well.

Use metrics to make decisions

Want to a) kill a metrics program, b) get a lot of people mad at you, and c) fail at an importance aspect of your job? Then pay no heed to applicable metrics when making a decision where the collected data could prove informative and valuable.

A reasonable person might say, "Well, duh." But I’ve seen this happen multiples times within multiple organizations, and the end-result is never good–particularly in terms of morale.

No one should be a slave to the data, but if you can’t legitimately explain why you’re opting for what’s in the Box when all the applicable data says to take what’s behind Door #2, you’re demonstrating a flagrant disregard for the agreed-upon decision-making and encouraging others to play the same way.

Remember: Metrics are not maces

It can be really, really tempting at times to wield metrics like a mace and figuratively bash in the heads of those who seem happily misinformed and proud of their ignorance.

Don’t do it.

By all means, convey the information in a way that it can be received and processed. But if you set an example of using data as a weapon, it suggests that others do the same — which inevitably contaminates the data as it gets twisted, sometimes right at the source, in a nuclear arms race where nobody wins and the organization suffers.

"It’s Not My Fault!"

People are going to feel how they’re going to feel and react how they’re going to react. But if you use the right mix of metrics to get a full view of the product; use metrics in your decision-making; and create a context where data is use constructively — to solve problems rather than assign blame — then you’re on your way to diffusing the danger of collecting metrics and using them to propel your product forward.

 

Chris leads product management for the Lycos Network’s games division, including Gamesville.com and white label game solutions. Prior to Lycos, Chris served as product manager for GameLogic, Inc., where he drove alignment among business, technical, and creative resources to create casino-style online games for land-based casinos in the United States and the United Kingdom. These games are available at Foxwoods Resort & Casino, Dover Downs, and Trump Taj Mahal Casino Resort, among others. Chris graduated with distinction from Merrimack College with a degree in English and a minor in Religious Studies. He received a Master of Business degree from University of Phoenix.

Interested in being a Guest Blogger on The Product Guy? Contact me.

Why Startups are Agile and Opportunistic – Pivoting the Business Model

steve_blank Guest post by Steve Blank, of Steve Blank dot com.

Startups are the search to find order in chaos.
Steve Blank

At a board meeting last week I watched as the young startup CEO delivered bad news. “Our current plan isn’t working. We can’t scale the company. Each sale requires us to handhold the customer and takes way too long to close.  But I think I know how to fix it.” He took a deep breath, looked around the boardroom table and then proceeded to outline a radical reconfiguration of the product line (repackaging the products rather than reengineering them) and a change in sales strategy, focusing on a different customer segment. Some of the junior investors blew a gasket. “We invested in the plan you sold us on.” A few investors suggested he add new product features, others suggested firing the VP of Sales. I noticed that through all of this, the lead VC just sat back and listened.

Finally, when everyone else had their turn, the grey-haired VC turned to the founder and said, “If you do what we tell you to do and fail, we’ll fire you. And if you do what you think is right and you fail, we may also fire you. But at least you’d be executing your plan not ours. Go with your gut and do what you think the market is telling you.  That’s why we invested in you.”  He turned to the other VC’s and added, “That’s why we write the checks and entrepreneurs run the company.”

The Search for the Business Model

A startup is an organization formed to search for a repeatable and scalable business model.

Investors bet on a startup CEO to find the repeatable and scalable business model.

Unlike the stories in the popular press, entrepreneurs who build successful companies don’t get it right the first time. (That only happens after the fact when they tell the story.) The real world is much, much messier.  And a lot more interesting. Here’s what really happens.

Observe, Orient, Decide and Act

Whether they’re using a formal process to search for a business model likeCustomer Development or just trial and error, startup founders are intuitively goal-seeking to optimize their business model. They may draw their business modelformally or they may keep the pieces in their head. In either case founders who succeed observe that something isn’t working in their current business model, orientthemselves to the new facts, decide what part of their business model needs to change and then act decisively.

(A U.S. Air Force strategist, Colonel John Boyd, first described this iterative Observe, Orient, Decide and Act (OODA) loop. The Customer Development model that I write and teach about is the entrepreneur’s version of Boyds’ OODA loop.)

Pivoting the Business Model

What happens when the startup’s leader recognizes that the original business model model is not working as planned? In traditional startups this is when the VP of Sales or Marketing gets fired and the finger-pointing starts. In contrast, in a startup following the Customer Development process, this is when the founders realize that something is wrong with the business model (because revenue is not scaling.) They decide what to change and then take action to reconfigure some part(s) of their model.

The Customer Development process assumed that many of the initial assumptions about your business model would probably be wrong, so it built in a iteration loop to fix them. Eric Ries coined this business model iteration loop – the Pivot.

(One of the Pivot’s positive consequences for the startup team is realizing that a lack of scalable revenue is not the fault of Sales or Marketing or Engineering departments – and the solution is not to fire executives – it’s recognizing that there’s a problem with the assumptions in the initial business model.)

Types of Pivots

“Pivoting” is when you change a fundamental part of the business model. It can be as simple as recognizing that your product was priced incorrectly. It can be more complex if you find the your target customer or users need to change or the feature set is wrong or you need to “repackage” a monolithic product into a family of products or you chose the wrong sales channel or your customer acquisition programs were ineffective.

If you draw your business model, figuring out how to Pivot is simpler as you can diagram the options of what to change. There are lots of books to help you figure out how to get to “Plan B,” but great entrepreneurs (and their boards) recognize that this process needs to occur rapidly and continuously.

Operating in Chaos + Speed + Pivots = Success

Unlike a large profitable company, startups are constrained by their available cash. If a startup does not find a profitable and scalable business model, it will go out of business (or worse end up in the “land of the living dead” eking out breakeven revenue.)  This means CEO’s of startups are continually looking to see if they need to make a Pivot to find a better model. If they believe one is necessary, they do not hesitate to make the change. The search for a profitable and scalable business model might require a startup is make multiple pivots – some small adjustments and others major changes.

As a founder, you need to prepare yourself to think creatively and independently because more often than not, conditions on the ground will change so rapidly that your original well-thought-out business model will quickly become irrelevant.

Summary

Startups are inherently chaotic. The rapid shifts in the business model is what differentiates a startup from an established company. Pivots are the essence of entrepreneurship and the key to startup success. If you can’t pivot or pivot quickly, chances are you will fail.

Pivot.

Lessons Learned

  • A startup is an organization formed to search for a repeatable and scalable business model.
  • Most startup business models are initially wrong.
  • The process of iteration in search of the successful business model is called the Pivot.
  • Pivots need to happen quickly, rapidly and often.
  • At the seed stage, microcap funds/ superangels understand that companies are still searching for a business model – they get Pivots.
  • Most of the time when startups go out for Series A or B round, the VC assumption is that a scalable business model has already been found.
  • Pivots are why startups must be agile and opportunistic and why their cultures are different from large companies.

Steve Blank currently teaches entrepreneurship at U.C. Berkeley Haas Business School and at the Stanford University Graduate School of Engineering. Over the last 25 years, he has been part of, or co-founded eight Silicon Valley startups (MIPS, Zilog, Rocket Science, SuperMac, Convergent Technologies, Ardent, ESL, and E.piphany). Steve teaches a methodology of starting and managing marketing, sales and business development in high technology startups that you can read more about on his blog self-titled blog, Steve Blank.

Interested in being a Guest Blogger on The Product Guy? Contact me.

The Product Guy: Superfine in 09

Snowman&Bell The Product Guy had another superfine year in 2009, sharing and exploring products, their experiences, and many innovative startups and the founders behind them, while getting to meet and speak with many of The Product Guy’s steadily growing readership.

And, as 2009 comes to a close, as I did last year, let’s take a brief look at the top posts that made this year on The Product Guy so totally superfine….

 

#9 Quick-UX Credibility from Likexo to Etsy

Quick-UX Credibility is a measure of the starting point, the foundation of a product’s Credibility. A look at the popular (and not so popular) examples of web product Credibility online.

image

#8 World’s Best Programmer is… [w/ Respect]

The World’s Best Programmer wants respect.

And, respect is just one of those conditions prevalent within the environment of the World’s Best Programmer. In this last post in the series The Product Guy reveals just who exactly is World’s Best Programmer, and where/how they thrive!!

image

#7 Converted by an Android. A short story of Gmail, in parts.

Part 1 in a series exploring the eventual adoption of Gmail in one’s daily life, by one once thoroughly addicted to, dependent on, the primarily client-based solution of Microsoft’s Outlook, what brought about this conversion, why it took so long, and what should be done to encourage greater Gmail adoption.

image 

#6 jQuery Plugin: It’s CuteTime!

Many online social products, and more continue to, avoid a formal timestamp format… 2009-10-10 23:14:17 and Thu, October 29, 2004 12:14:19 PM … opting for more user friendly, "warm and fuzzy," human-readable styles… 9 days ago and 5 years ago.

As a result, the time has come for the jQuery CuteTime plugin. CuteTime goes beyond similar tools and lets you easily: convert timestamps to ‘cuter’ language-styled forms (e.g. yesterday, 2 hours ago, last year, in the future!), customize the time scales and output formatting, and dynamically update the displayed CuteTime(s) upon request and/or automatically.

image 

#5 The Future: Gmail, Social Media, and You

Over the past many weeks I have explored, elaborated, and exhausted the extent of the then existent exercising of resistance. Now, with such resistance eroded, drawn out through my conversion by an Android, an exploration into the Future of Gmail and the ‘Should Do’ … Readability, Simplify, Organize, Integration and Consistency.

image 

 

#4 Google: True Colors Shine Through

In answering the question of Desirability, "Do I want it?" the sub-category of Color Scheme plays an important role. Google Search is an outstanding example of a Good Color Scheme demonstrating alignment of both colors and messaging. Learn from it.

image

#3 Stardoll: Lost and Naked

When you look at a web page, the various elements of the page can often be seen coalescing into distinguishable regions and groups. Intentionally structured, or otherwise, these groups that constitute the page Layout play an important role in the web product’s Desirability. Stardoll is a great example of a web product with Poor Sequential Flow.

image 

#2 ThreeDots: The jQuery Ellipsis Plugin

Many online products employ ellipses within their products to improve various aspects of the User Experience, such as: allowing for easy summary scanning of page content, and fitting more diversity of content into a smaller space.

As a result, the time has come for the jQuery ThreeDots plugin. ThreeDots goes beyond similar tools and lets you easily and smartly truncate text for when: text is too long, text doesn’t fit within the available space, you want to employ highly configurable and flexible ellipses within your web product.

image 

#1 Quick-UX. Quick Heuristics for User eXperience.

Quick-UX provides for the rapid, simple and quantifiable assessment of a product’s User Experience (UX), consisting of the core components of Usability (‘Can I use it?’), Usefulness (‘Should I use it?’), and Desirability (‘Do I want to use it?’). 

Quick-UX provides a sure-fire, rapid way to obtain concrete and comparable means by which to assess a single product or compare its strengths and weaknesses to other products.

Growing in popularity by leaps and bounds since its original posting in 2008, this posting has earned prime placement amongst other, more recent, articles that made this year, 2009, SUPERFINE.

image

 

theproductgroup_logo_200909_thumb75
balsamiq_logo2_thumb26

This year also saw the launch of The Product Group (sponsored by Balsamiq Studios) in NYC as an opportunity for Product People of all sorts and levels of experience to meet, interact, and network, in a laid-back, conversational environment.  I am certain 2010 will bring many more exciting gatherings, discoveries, and opportunities; and for those reasons, this too, also helped make 2009 for both Product People and The Product Guy, superfine!

Group_Pic_1_20091001 DSC05663 DSC05662 DSC05661

Happy Holidays!

Jeremy Horn
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Google Add to Mixx!

World’s Best Programmer is… [w/ Respect]

anotherstar … motivated, excited and productive. And she, or he, may be sitting right next to you.

The prevailing element cited by all those who participated within this series or provided suggestions for World’s Best Programmer was Respect. From UltraRob discussing the understanding of ‘why’…

UltraRob Says:
February 26, 2009 at 1:02 pm

Most programmers are very self motivated. We like to solve problems and create cool things. Sure we sometimes need to be guided to focus on things that make business sense but if we’re given the information to see what is important that usually isn’t a problem.

From my perspective programmers don’t need much to be motivated but many managers don’t understand what it takes. For me it’s the little things that make me feel respected and take ownership. I don’t even have to agree with decisions as long as I understand why the decision was made and my view was heard. If I’m given those things, I’m pretty unstoppable.

…to Chris Geier’s nomination of Mike Scheider as World’s Best Programmer

chrisgeier: @theproductguy Mike Schneider. Does the amazing in limited time, and is always looking to do it better. A great quality

…the one element, evident throughout the successful implementation of all of the previously discussed characteristics, as well as noted in almost all of the feedback received is Respect.

Motivation

My answer is many fold and I provide a framework towards greater understanding in part 1.

The path to the motivated programmer, the happy programmer, is unique to each individual. There are, however, some general, instructional guides towards better understanding for all involved parties, and especially regarding those conditions that make for that highly motivated programmer.

Let’s take a deeper look at Respect.

Respect

If Communication is the glue that binds together the environment of the World’s Best Programmer, from Clarity to Inclusion, then Respect can logically be seen as the glue’s glue, the foundational element upon which the rest is built.

Without Respect between programmers, between programmers and managers, and any other relevant permutations of these, no one, not even the World’s Best Programmer, can thrive. The key characteristics described throughout this series…

    • Clarity
    • Organization
    • Focus
    • Communication
    • Inclusion
    • Challenge
    • Respect

… cannot be built upon without the most basic foundation of them all, Respect.

Respect, more importantly, MUTUAL Respect, a 2-way relationship, comes from all parties establishing and fostering mutual credibility and understanding. It is something that either exists or is lacking in the whole. If Respect is not mutual, then it can be truly said to be lacking. If Respect only flows in one direction, the effect on the individual on the receiving end is negligible since the source is not respected and, therefore, is not valued.

Building Respect

Sometimes easier to accomplish than others, most difficult if already lost, there are some examples that everyone, from programmer to manager, can learn from.

Micromanaging. Getting overly involved in a technical process for which you will not be directly creating, no matter the intention (e.g. "to help") is most frequently interpreted as a lack of trust, either of skills, and/or Respect, for co-worker space.

"So Easy." Don’t be the individual known for telling other programmers "Oh, that’s so easy." Programmers consider boundary cases, scaling, etc. which are not always "so easy." Just because a high-level business case is simple, its simplicity does not necessarily extend to the technical implementation. Exclaiming such simplicity often minimizes programmers’ skills, and, in turn, their Respect for individuals making these broad assumptions.

Corollary: Time. Make sure everyone has the time to do things properly. It, of course, goes to say that everyone is communicating about time constraints and other requirements associated with the "things to be done."

Explain. Don’t assume everyone is on the same page when it comes to methodologies and processes. Whether you are a programmer or a manager, explain and clarify the processes. For example, when projecting that a task will take X time, explain the ‘what’ and the ‘why’ behind the methods and logic of the projection.

Strength. Present strength with clarity. When working with other programmers, do not mislead them about the level of influence you have in the processes, or their change.

  • Stand up against feature creep.
  • Stand up for your programmers / co-workers / managers (from time to disruptions).
  • Don’t promise what cannot be delivered.

World’s Best

anotherstar The World’s Best Programmer may be sitting right next to you, maybe it’s you. Every programmer has that potential and it is up to everyone; programmer, manager, and organization to carefully craft and maintain the environment with the characteristics…

Clarity. Providing clear project requirements and goals.
Organization. Balancing the art and science, of programming, through structure.
Focus. Removing distractions and hurdles.
Communication. Promoting openness, free flow of ideas and information, and teamwork.
Inclusion. Empowering throughout all aspects, from idea origination to release and support, from business facing to backend, of the product processes.
Challenge. Fostering growth, new learning, and meaning.
Respect. Establishing and fostering mutual credibility and understanding.

Through careful thought and application of the characteristics discussed throughout this series you may soon become, meet, or be introduced to the World’s Best Programmer.

Subscribe now (click here) to make sure you don’t miss any part of this series highlighting many of the key driver’s of your team’s motivated programmers, nor other insightful posts from The Product Guy.

Enjoy!

Jeremy Horn
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Magnolia Google Add to Mixx!

World’s Best Programmer is… [w/ Challenge]

anotherstar …to be announced at the end of this series.

unkown-person I am often asked what is it that I do that results in the programmers with whom I interact being so productive; what is it I do to get them motivated and to keep them motivated; and where can I find / who is the World’s Best Programmer.

Motivation

My answer is many fold and I provide a framework towards greater understanding in part 1.

The path to the motivated programmer, the happy programmer, is unique to each individual. There are, however, some general, instructional guides towards better understanding for all involved parties, and especially regarding those conditions that make for that highly motivated programmer.

Today, let’s take a deeper look at Challenge.

Challenge

Challenge can be seen as a double-edged sword. Challenges surround programmers each and every day, both as motivators and demotivators. While not necessarily a driver of success in every programmer, some prefer to keep it simple and focus on the familiar and ‘what they are good at.’ Nonetheless, leveraging Challenges towards positive outcomes is very prevalent where good programmers are found, especially within the environment of the World’s Best Programmer.

Challenges that foster …

  • personal and career growth,
  • new learning, and
  • meaning

… represent the best drivers of excitement and reward.

Many programmers will always be able to find fun, productive, and new ways to Challenge themselves simultaneously benefiting those around them.

Other programmers may seek a challenge that provides that personal meaning, but require a little guidance. Work with programmers and assist them in finding or building upon Challenges that are new and exciting to them. Reinvigorating a common task or a persistently onerous effort through finding that Challenging, motivating spark will bring new life and engagement to both the work and the programmer.

Different programmers are motivated by finding different, personally appealing, Challenges in their daily work. These Challenges can be anything from …

  • Optimizing speed or memory,
  • Reducing the total number of source code lines,
  • Satisfying the needs of a client,
  • Maximizing modularity and reusability, and/or
  • Crafting that perfect algorithm.

Competition

One way to build an environment with positive challenges is to support the many seeds already present in the form of friendly competition. Such friendly competition, when appropriately encouraged and reinforced is great in the establishment of a self-sustaining, self-organizing system of motivational Challenges.

Friendly competitions can take on the form of total number of tasks completed, to fastest execution, to more broadly inclusive contests for ‘coolest’ app.

Leverage

Within an atmosphere of open Communication it becomes easier to learn how to transform problems that demotivate into those that Challenge in a rewarding way (for the programmer, as well as many more within the organization).

No Limits

A common mistake when thinking about what sort of ventures are best for Challenging programmers is to stereotype and only think technically. There are many ways a programmer may be seeking to grow in their job that can equally be great motivators of success, from tech, to business, to peer interaction. Keeping the Challenges varied and the communication flowing will help identify those tasks (perhaps not previously even realized by the programmer) that bestow new and meaningful experiences. These could be such activities as being a manager for a product or learning to be a better communicator or more socially engaged with the non-technical groups.

……………

From the good programmer to the World’s Best, Challenge them and provide new ways to give meaning and value to their work.

The Search Continues

In addition to…

Clarity, Organization & Focus
Communication & Inclusion
Challenge

… and before this individual, World’s Best Programmer, is announced, the characteristics…

Respect

… will be further explored and discussed in the subsequent articles of this multi-part series.

Subscribe now (click here) to make sure you don’t miss any part of this series highlighting many of the key driver’s of your team’s motivated programmers, nor the denouement of World’s Best Programmer, as well as other insightful posts from The Product Guy.

Enjoy!

Jeremy Horn
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Magnolia Google Add to Mixx!

World’s Best Programmer is… [w/ Inclusion]

anotherstar …to be announced at the end of this series.

unkown-person I am often asked what is it that I do that results in the programmers with whom I interact being so productive; what is it I do to get them motivated and to keep them motivated; and where can I find / who is the World’s Best Programmer.

Motivation

My answer is many fold and I provide a framework towards greater understanding in part 1.

The path to the motivated programmer, the happy programmer, is unique to each individual. There are, however, some general, instructional guides towards better understanding for all involved parties, and especially regarding those conditions that make for that highly motivated programmer.

Today, let’s take a deeper look at Inclusion.

Inclusion

I have already included certain aspects of Inclusion under the discussion of the importance of Communication to the environment of the World’s Best Programmer, so the following represents my continued thoughts and emphasis on this feature.

Communication encompasses the mechanisms by which ideas and the knowledge base, in general, are transmitted throughout the organization. While some organizations believe that there are only a select few who “need to know,” studies of effective organizations have demonstrated that it is important from a morale (and subsequently, a productive) standpoint for knowledge to be shared as much as possible. In that way, everyone working on a project understands the value and interrelatedness of their individual efforts and can then take pride in its successful completion/outcome.

Inclusion is an atmosphere of valuing the members of the organization for those contributions. While channels of communication promote Inclusion, it is only when those channels become institutionalized that individuals feel included. Saying everyone’s efforts are valued is one thing. Demonstrating that the organization truly does that takes place over time through repetitive actions that serve to strengthen that value in the organization.

True Inclusion is “in the air.” It is one thing to put in channels for communication, but it is also necessary that there be respect for the communications, and acceptance of communications, and the organizational value that every programmer just believes and accepts that this will occur.

On a more basic level, Inclusion in any organization is embodied by practices that have become part of the culture (second nature) that the contributions of all are anticipated and valued. If there is not a sense of Inclusion in an organization, the cost can be high, both in terms of money and time. Different perspectives do not see the light of day and are therefore not considered. No matter the channels of communication that are put in to place, if the programmer does not believe the organization values Inclusion, they may/will be reluctant to propose what may prove to be a more viable solution.

Examples of building that culture of Inclusion are…

Junior Programmers. Teach junior programmers, and team members, how senior people throughout the organization make decisions. Even though the junior individuals may not have a measurable impact on the end result of, or introduce a small cost of educational overhead to, meetings, being included and understanding what results in one idea being accepted over another, or why one approach is considered superior to an alternate, helps everyone feel more a part of the process, learn a thing or two, and become a stronger contributor.

Early. Get the technical individuals and other programmers involved early in a project. As the more business-oriented, or technically-oriented, components of the organization begin making the plans, both sides will benefit from mutual Inclusion helping one another steer toward much easier, cost-effective solutions and approaches.

The Search Continues

In addition to…

Clarity, Organization & Focus
Communication & Inclusion

… and before this individual, World’s Best Programmer, is announced, the characteristics…

Challenge & Respect

… will be further explored and discussed in the subsequent articles of this multi-part series.

Subscribe now (click here) to make sure you don’t miss any part of this series highlighting many of the key driver’s of your team’s motivated programmers, nor the denouement of World’s Best Programmer, as well as other insightful posts from The Product Guy.

Enjoy!

Jeremy Horn
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Magnolia Google Add to Mixx!

World’s Best Programmer is… [w/ Communication]

anotherstar …to be announced at the end of this series.

unkown-person I am often asked what is it that I do that results in the programmers with whom I interact being so productive; what is it I do to get them motivated and to keep them motivated; and where can I find / who is the World’s Best Programmer.

Motivation

My answer is many fold and I provide a framework towards greater understanding in part 1.

The path to the motivated programmer, the happy programmer, is unique to each individual. There are, however, some general, instructional guides towards better understanding for all involved parties, and especially regarding those conditions that make for that highly motivated programmer.

Today, let’s take a deeper look at Communication.

Communication

You can’t get anything accomplished without good Communication. Everyone, from CEO to manager to the World’s Best Programmer, knows that. Many different professions and skill-sets come with their own special keywords, languages, and manners. Sometimes this difference could not be more obvious than when it is demonstrated between manager and programmer, even within the environment of World’s Best Programmer.

Inadequate or poor Communication leads to a programming environment characterized by …

Distrust,

Confusion, and

Paranoia.

These conditions, like a disease, will demotivate and crush the spirit and productivity of any programmer, from the good to even the World’s Best; and, like a disease, can fester and eat away at the core of any product, team, and organization. And, as is the nature of this illness, it is harder to correct once it takes root, since discovery would entail having good Communication.

Open

An open environment wherein people are comfortable expressing their thoughts, where they don’t feel ignored, is where the World’s Best Programmer is found. And, by open, I am not referring to an environment defined by shouting, or disorder. It is a structured environment, where teamwork flourishes, and authority is respected on par with the feedback, ideas, and other issues brought up and discussed, regardless of ‘rank.’ It is an environment within which the programmer is comfortable questioning, and suggesting alternatives, all the while expecting that his thought s will be respected. While they need not be accepted, they are at least considered.

Some exemplary steps and practices that can lead to this motivational, empowering environment are…

Passion. Having passion in one’s work is very important and can be very constructive for many individuals — nurturing friendly, healthy competition in many. However, passion should be carefully targeted in both good and bad situations. When passions are appropriately checked, when tone is stern, not angry, care taken for understanding technical complexities, fear and unease are reduced, or eliminated, enabling all to speak-out about problems before they get worse (or it is too late).

Leave. For some managers it is reflexive to just ‘let the programmers be.’ Such behavior is often the result of the discomfort associated with finding a common language and grasping necessary programmer concepts. For others, this behavior may come from the flawed logic that to ‘let the programmers be,’ steering clear of them, minimizing the Communication is a sign of trust and respect.

Simply put, for managers of this sentiment, leave your office; interact. Interaction breeds teamwork and understanding. Present an environment where business meetings are equally important as those meetings with programmers, always working towards establishing and enhancing community and commonality.

For example, perhaps once a day outside of the normal meetings or, perhaps on recurring dates and times (see Focus for more information), briefly walk around observing, learning, and Communicating.

Interest. It is important to not feign interest in the issues of programmers. Furthermore, as a manager of programmers, don’t simulate knowledge of programming topics and challenges – as is the inclination for too many.

When items are discussed with programmers, follow-up; if you don’t understand something, ask questions. Be patient, as it may be difficult to convey some concepts; but, through the demonstration of valuing the programmers’ thoughts, opinions, and insights, each individual will better understand the starting points of understanding for the respective parties and allow for the converging of minds.

Through the simple practice of demonstrating that you value the opinions of the programmers, through action demonstrating your interest in feedback from programmers, by following-up and being accessible (not forcing people to have to leave their programmer to ‘chase you down’) Communication is improved – paving the way for an ever greater number of open and frank conversations.

Squash any ethos of secrecy, demonstrate trust through inclusion and open Communication, and, in turn, you will provide the motivational drivers to propel your programmers to succeed, within which environment, too, can be found the World’s Best Programmer.

The Search Continues

In addition to…

Clarity, Organization & Focus
Communication

… and before this individual, World’s Best Programmer, is announced, the characteristics…

Inclusion
Challenge & Respect

… will be further explored and discussed in the subsequent articles of this multi-part series.

Subscribe now (click here) to make sure you don’t miss any part of this series highlighting many of the key driver’s of your team’s motivated programmers, nor the denouement of World’s Best Programmer, as well as other insightful posts from The Product Guy.

Enjoy!

Jeremy Horn
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Magnolia Google Add to Mixx!

World’s Best Programmer is… [w/ Focus]

anotherstar …to be announced at the end of this series.

unkown-person I am often asked what is it that I do that results in the programmers with whom I interact being so productive; what is it I do to get them motivated and to keep them motivated; and where can I find / who is the World’s Best Programmer.

Motivation

My answer is many fold and I provide a framework towards greater understanding in part 1.

The path to the motivated programmer, the happy programmer, is unique to each individual. There are, however, some general, instructional guides towards better understanding for all involved parties, and especially regarding those conditions that make for that highly motivated programmer.

Today, let’s take a deeper look at Focus.

Focus

Many very good programmers will frequently feel the pull of new technologies, newer more exciting projects, tangential and/or ‘very cool’ innovations. It is very important to allow for the artistic, curious, knowledge seeking side of every programmer to be able to explore exciting alternatives, from new hardware and languages to discussions on new technologies, new vendor tools and other programmer-y things.

However, it is also very important to facilitate the needed Focus that will empower the programmer to stay on track and on schedule, to be able to point to front-line accomplishments while also allowing for the time for growth. ‘Exploration time,’ as can also be seen in the case of the World’s Best Programmer, announced at the end of this series, can result in …

  • Fresh ways of thinking,
  • New and exciting group discussions,
  • Constructive and illuminating debates, and
  • Company-applicable ideas and solutions.

Facilitating Focus

Helping a programmer with Focus can be as simple as implementing some of the Organizational tips already discussed, or limiting general business-side Q&A to specific times of the day/week. Further examples on delivering oft sought after Focus are …

Process. In offices where the programmers share the dual-responsibility of creating and maintaining, or overseeing, production support to keep the organization running smoothly and rapidly addressing bugs and the common real-time production issues, the introduction of processes for the minimization of work-stopping, deadline-killing, frustration-inducing, time-and-money-wasting, Focus-sapping distractions are truly useful.

For example, instead of everyone sharing simultaneous oversight of production, have a rotating schedule where one individual (or a subset of the team) is on-call for a specific day. And, while this individual, with all production issues diverted their way, is focused on the short-term handling of ‘putting out fires,’ the remaining team is 100% removed from the fray and 100% Focused, shielded from the issues of production, empowered to Focus, on their current projects, deadlines, strategic long-term planning, design, etc.

Scheduling. As I briefly touched on above, ‘exploration time’ is an important part of any programmer’s growth in their job, spent on anything from reinforcing the basic to exploring the latest, coolest framework. However, as most can relate, when you are working on that cool thing, or deeply focused on learning a concept, other action items can quickly fall by the wayside.

Every programmer should have time for exploration. Simply allot that (sacred) time in the programmer’s schedule, appropriately take into account this time in project scheduling, and provide clear business deliverables. To bring more structure to this ‘exploration time,’ provide a recurring venue (e.g. monthly lunch) for people to share their own goals, findings, and accomplishments with one another; in turn, this results in ‘exploration time’ being a valuable experience for all, existing within a focused environment, not distracting nor detracting from the business milestones or long-term strategic goals of the company.

Prioritization. A fundamental characteristic present in the environment of the World’s Best Programmer is Prioritization and the added boost in productivity over the loosely prioritized or non-prioritized list they receive. Such Focus supporting prioritization can be achieved through the maintenance and presentation of a personalized short-list of to-do items to each individual programmer within the organization. The list should consist of clear priorities, with no overlapping / identical priorities, so the programmer can work on each item, one at a time. As a society, we often make claims of being able to juggle multiple, simultaneous projects and priorities – more recent studies …

… have proven this to be false, misguided, and harmful to productivity and correctness. As a very wise programmer once told me, as I tell you here today, “while we like computers to multi-process as much as possible, having humans do that usually comes with a price of context switch and mistakes from lack of focus.”

For Focus

A good programmer, as does the World’s Best Programmer, will value the freedom to explore and learn, but equally value, and be motivated through, the successful efforts you take to help remove unnecessary distractions and provide for an environment that permits Focus on their short-and long-term goals.

The Search Continues

In addition to…

Clarity, Organization & Focus

… and before this individual, World’s Best Programmer, is announced, the characteristics…

Communication & Inclusion
Challenge & Respect

… will be further explored and discussed in the subsequent articles of this multi-part series.

Subscribe now (click here) to make sure you don’t miss any part of this series highlighting many of the key driver’s of your team’s motivated programmers, nor the denouement of World’s Best Programmer, as well as other insightful posts from The Product Guy.

Enjoy!

Jeremy Horn
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Magnolia Google Add to Mixx!

World’s Best Programmer is… [w/ Organization]

anotherstar …to be announced at the end of this series.

unkown-person I am often asked what is it that I do that results in the programmers with whom I interact being so productive; what is it I do to get them motivated and to keep them motivated; and where can I find / who is the World’s Best Programmer.

Motivation

My answer is many fold and I provide a framework towards greater understanding in part 1.

The path to the motivated programmer, the happy programmer, is unique to each individual. There are, however, some general, instructional guides towards better understanding for all involved parties, and especially regarding those conditions that make for that highly motivated programmer.

Today, let’s take a deeper look at Organization.

Organization

Programming is both an art and a science. The art can be found in requirements that a program must not just work, but be aesthetically pleasing (easy to maintain and understand, and sometimes enjoyable, appreciated and admired) to current, and future, programmers. The science keeps everything coordinated and efficiently functioning in harmony — be they the programming efforts of a team of one, or many.

And through, as well as with, the sciences and scientific arts come the call, the requirement, for Organization, and some basic steps and examples that can assist in creating an environment of Organization – within which is found the World’s Best Programmer.

For Example

Empower the programmer(s) with an organized, structured work environment. Such structure should clearly delineate which individuals are responsible for accomplishing/providing what and when. Clear processes avoid confusion. At a minimum, very clear processes should exist, and be succinctly documented, for…

Meetings. A daily (or regularly recurring) update meeting, where people can share their task status updates with the rest of the group and highlight challenges and potential project conflicts with potentially relevant parties, is very valuable. All meetings do not have to be, nor should they be, longer than is useful, but they should occur like clockwork, on specific days and times, with no exceptions (even if the next meeting is to give everyone a quick 30 second update that there are no updates). This institution of sacred meeting time builds regularity and consistency into the often overlooked value of information and knowledge sharing — and can be a central driver of all of the other highlighted programmer motivational tips.

Development. From the origination of a project idea through to business analysis, design, development, QA, acceptability testing and final project release there should exist very clear, ordered processes for working within each stage and regarding movement of a project from one stage to another.

And, as a corollary, the necessary tools and resources needed to accomplish the various tasks should also be made available to further bolster the Organization and consistency of the environment. For example, everyone should be making use of the same version control software, as well as applying the same procedures for checking-in, -out, and promoting the versioned content.

Furthermore, a well organized environment will be one within which goals and processes are clear, wherein the end goals can be clearly understood without overburdening any individual with excessive details beyond those needed for the current and upcoming tasks. This, while simultaneously allowing for the ease of access to deeper knowledge along with capabilities to be flexible and adapt to changing goals and business cases, will create an environment that breeds great programmers and, in which, the World’s Best Programmer is found.

The Search Continues

In addition to…

Clarity & Organization

… and before this individual, World’s Best Programmer, is announced, the characteristics…

Focus
Communication & Inclusion
Challenge & Respect

… will be further explored and discussed in the subsequent articles of this multi-part series.

Subscribe now (click here) to make sure you don’t miss any part of this series highlighting many of the key driver’s of your team’s motivated programmers, nor the denouement of World’s Best Programmer, as well as other insightful posts from The Product Guy.

Enjoy!

Jeremy Horn
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Magnolia Google Add to Mixx!