Networking For First Time Entrepreneurs

Effective networking is an extremely important tool for first time entrepreneurs.  Irrespective of target goals – meeting potential investors, finding business partners, establishing technology partnerships, or simply spreading the word around about your new venture – networking provides the necessary channels to meet those goals if utilized properly.

Robert Ochtel offers some good tips on “dos and don’ts” of networking for first time entrepreneurs in his blog post titled ‘Some Truths About Networking for First Time Entrepreneurs‘.  I especially like his comment on how networking is really focused “Socializing”:

“Networking is really no different than any other socializing activity. In fact, if it were referred to as “socializing”, instead of networking, I believe it would be less intimidating to first time entrepreneurs. The word “networking” seems to have an underlying performance-based stigma associated with it………A better approach is to attend each networking event with a positive attitude and hope to meet one to two individuals you can possibly create a personal connection with.”

It’s true that people are far more relaxed in social settings (with friends and family or casual gatherings) than in networking events.  As Robert points out, this is due to “performance based stigma” associated with networking events that creates an expectation of walking away with contacts that are potentially valuable for you or your venture.  In this case, the concept of “value” is essentially misplaced.  Networking rarely generates the type of contacts and relationships that create an immediately impact on your venture overnight — for example, you cannot meet an investor and expect him to invest in your company immediately.  Instead, focus must be on cultivating mutually beneficial, long term relationships that might potentially add value to you and your venture in the long term.

Following up with the contacts you meet at any event within a week or so of that event is also important step in building a relationship with that contact.  Networking does not end when you meet a person at a conference or an event – but continues way beyond the event.  When you meet someone at a networking event, you are just someone they “met at an event” – like many others they might have met that day at that particular event.  Following up  and maintaining a continuous dialogue will give you an opportunity to distinguish yourself from the pack and stand out.

Here are some “do’s and don’ts”  of following up and keeping an open ended conversation going:

To expand on the “targeted networking” Robert talked about i his post, here are a few more tips on how to network effectively.

Networking is a tough but crucial component of the first time entrepreneur’s overall strategy for personal and professional success.  I myself am practicing most of the tips from above and from Robert’s post — and several others are already on my networking road map.

Got any more tips on networking for first time entrepreneurs ?  Share them here.  In the mean time, get out there and start networking !

Enhanced by Zemanta
Entrepreneurship, Networking

Why Do We Need Visual Models ?

modelsOne of the questions that often comes up during a discussion on Model Driven Development is “why do we even need visual models”?  The question varies based on the experience and extent of use of modeling within the target audience – but the essence of the question remains the same.

Modeling is an inherent part of human life — as they say “a picture is worth a thousand words”.  A picture can communicate information better by hiding the complexities and displaying only the relevant details.  For example, when we look for directions we tend use the map representation instead of the textual directions as the map provides us with just enough details to visualize the directions.  Models also have been used in several disciplines including science and engineering for a long time.   CAD/CAM models are used in engineering to model engineering parts and structural models are used in architecture to model large structures and buildings.  Irrespective of the problem domain, models provide a simplified abstraction of the complexity involved in that domain.  While models do not have to be visual, most models are visual and the visual representation further adds to minimization of complexity.  Different models can be used to capture different characteristics of the problem domain and the type of diagrams used to visualize the model of a specific problem domain really depends on the problem domain itself.

Visual models have also been used in software engineering to different extents depending on the context, skills, time and tools available.  Depending on the size of the organization or team working on project and the complexity involved, no modeling step may be involved in certain implementations.  Developers go directly from requirements to coding and no models are produced during the lifecycle of the project.  In other cases, models drawn on white board are used to facilitate discussions around design ideas and modeling stops when the discussion ends.  In most cases, models are used primarily for communication among various groups involved during the early stages of the project – during requirements gathering, analysis and design.  The primary intent of these models is to capture a high level view of the system under consideration and to present a common view to all parties involved.  These models could be technical architectural diagrams, data models, use case models, class diagrams, sequence diagrams, etc., and are drawn using tools such as Powerpoint or Visio or a more formal UML modeling tool.  However, these models are thrown away once the development starts since it is hard to keep the code and models in sync as the requirements change during the remaining life cycle of the project.

Today’s systems are complex with many moving parts (thanks to modern multi-tier and distributed architectures) — models enable us to cope with this complexity by providing a visual abstraction layer that focuses on the higher level concepts in the problem domain and de-couple the “what” from “how”.  For instance, imagine trying to understand the dependencies in a large system by looking at the code vs. looking at visual design models (use case models, component diagrams, class diagrams and activity diagrams, etc.).  Depending on the level of detail desired, the needs of the target stake holder and the choice of architectural framework (TOGAF, Zachman, etc.), multiple views or perspectives of the entire enterprise architecture can be captured in various models including use cases, system architecture, data flows, object models, business processes, physical network, deployment nodes, system dependencies and database schemas, etc.

In summary, visual models provide us with the following important benefits:

As I mentioned earlier, in most traditional code-based development approaches, these models are merely used as design artifacts that provide a starting point for an extensive coding exercise where the higher level details captured in these models are translated into lower level details based on the target architecture.  What if the models we created are semantically 100% complete and are immediately executable instead of merely being design artifacts?  This is the promise of Model Driven Development and more on “Executable Models” later.

Enhanced by Zemanta
Modeling, Technical

SXSW Interactive 2009 – A Wrap Up !

I was in Austin over the weekend for the SXSW Interactive 2009 conference and wanted to share some thoughts and observations with everyone.  This was my first time at this conference and I truly did not know what to expect going in.  My decision to go to the conference was pretty much last minute and I didn’t have enough time to prepare properly for the conference — other than watching an intro video “How to Rock SXSW” by Shama Hyder of Shama.tv.

Anyways, here are some of my observations:

I attended several sessions and interactive panels – but the following three stood out for me in terms of the content and information they provided:

Looking back, I now realize that I did not take full advantage of many aspects of the conference.  In the end though, I am glad I attended as I walked away with more knowledge, information and potentially more relationships.  I really enjoyed the experience, the interactive panels and most of all the interaction with people with similar interests. It’s been a truly positive and inspiring experience !

I am sure I will be back next year — only better prepared to take advantage of everything the conference has to offer !

Ashok

Enhanced by Zemanta
Conferences, SXSW 2009