When it comes to running a start up, leaders need to make sure that their key players are motivated. This has been seen with many companies. Back in the 1970's it was found with the inspiration and diligence of the late Daniel Nigro when he formed Kleer-Fax. More recently it was seen in David Khasidy, the founder and recently retired president of SunRay Power Management, the most dynamic green energy leader in the US today.

The question is, what is it that great leaders like David Khasidy and Daniel Nigro do that make the difference? How do the most vulnerable companies (start ups) break the mold and become a part of our everyday lives?

It starts with their mission and vision.

Create a Strong Mission and Vision

There are many reasons why start ups fail. For one, they usually lack the capital to last through the lean times. Secondly, they often don't have the tolerance for setbacks that occur. Lastly, they do not have a long-term plan, also called a mission.

When a business has a strong mission, the team knows it and their focus toward their work and service to others within and without the company reflects that. To complement that, the shorter term vision of the company needs to be present as well.

This can even be seen in sole proprietorships with no employees, such as when Brian Pascale started his law practice. His vision was to find justice for his clients while his mission was to build upon a career that had already set precedents in the area of tort law.

As his practice has grown, new staff members can sense the vision and mission he exudes.

Encourage Ownership of Projects and Processes

Start ups need to inspire and motivate their employees because they need to know that they are not only a part of something important, but that their contributions mean something.

What won't happen if they are not there? What contribution do they make, and what are the consequences of them not fulfilling their part of the work?

By encouraging ownership in projects, team members can find that the work they are doing is not only important for the organization, but that they are going to be a big part of what makes it happen. The alternative is that they feel replaceable.

Offer Incentives That Keep the Company Competitive

When team members embrace the mission and vision of the company, and then take ownership for the company's success, they are going to need to be justly rewarded.

This could include flexible schedules (for those who don't need a stringent one), use of an account at a nearby takeout place, or even the potential for ownership as a result of a vesting program.

The incentive everyone is looking for more immediately, though, is cash. When the company takes in more revenue as a result of the efforts of those on the team, rewarding them can go a long way not only in making them feel appreciated, but in encouraging them to bring in more business.

Members of a start up team are usually very talented, and commonly underpaid. However, if they believe they are going somewhere, it will make a big difference.

Related:

Good non-programmer jobs for people with software developer experience

Smart Project Management –Best Practices of Good Managers

Project management could be one of the easiest jobs on the planet, and could also be the worst nightmare. The difference between the two extremes depends on smart management of a project. According to the project management institute, there are five phases in project management - Initiating, Planning, Executing, Monitoring & Controlling, and Closing.

Every manager has his own style of project management. But there are a lot of contributing factors that result in a successfully managed project. These factors vary from project to project, but they all contain some common elements.

1. Setting SMART Goals

I suspect that many of you are familiar with the term "hard coding a value" whereby the age of an individual or their location is written into the condition (or action) of a business rule (in this case) as shown below:

if customer.age > 21 and customer.city == 'denver'

then ...

Such coding practices are perfectly expectable provided that the conditional values, age and city, never change. They become entirely unacceptable if a need for different values could be anticipated. A classic example of where this practice occurred that caused considerable heartache in the IT industry was the Y2K issue where dates were updated using only the last 2 digits of a four digit number because the first 2 digits were hard-coded to 19 i.e. 1998, 1999. All was well provided that the date did not advance to a time beyond the 1900’s since no one could be certain of what would happen when the millennia arrived (2000). A considerably amount of work (albeit boring) and money, approximately $200 billion, went into revising systems by way of software rewrites and computer chip replacements in order to thwart any detrimental outcomes. It is obvious how a simple change or an assumption can have sweeping consequences.

You may wonder what Y2K has to do with Business Rule Management Systems (BRMS). Well, what if we considered rules themselves to be hard-coded. If we were to write 100s of rules in Java, .NET or whatever language that only worked for a given scenario or assumption, would that not constitute hard-coded logic? By hard-coded, we obviously mean compiled. For example, if a credit card company has a variety of bonus campaigns, each with their own unique list of rules that may change within a week’s time, what would be the most effective way of writing software to deal with these responsibilities?

Learning SQL development can seem like an overwhelming task at first. However, mastering just a few key points will help ease your way through 80 percent of the day-to-day challenges when writing stored procedures and solving common problems. Here are three important SQL development factors to keep in mind:

Outer Joins
One of the most crucial things to understand in SQL server are joins. Joins are a way to retrieve data from two or more tables based on logical relationships between them. Joins dictate how Microsoft SQL Server ought to use data from one table to select the rows in another table.

In my experience inner joins are intuitive while outer joins can present additional hours of grief by overlooking associations in the other table(s). The outer join is the key to answering questions about what the database does not have. For example, if you need to make a query to display all the students who are without report-cards, you’ll need a left join to get all students coupled with a “where clause” to return the ones who have nulls for their report card table columns in the results.

Many talented Java script programmers have muddled through the SQL Server by deficient coding around the inner join. As a result, their queries can take five hours to run, whereas, properly written left joins, can take only two seconds to run.

Aggregation
Grouping results comes up in SQL a lot more than you might think. Knowing how to write a query when answering questions such as, “What’s the average grade for each teacher’s student list?” is invaluable. This kind of question cannot be answered with a single table or solely by joins.  You’ll often find you need to use joins in conjunction with group by statements. Always write the raw query first and then look at the results. Next, you have to figure out the best way to group them, rewrite your select clause and add a group by clause in the end.

Digging Through Data
I find this is the most lacking skill in many programmers. In fact, many otherwise-talented programmers holding Master’s Degrees fail to get jobs because they couldn’t analyze rows of data objectively during interviews. It’s just something that’s not taught but is crucial to get under you belt. Why? Eventually, some query is not going to perform as you may expect. And, the only way to find discrepancies is to look at rows of data, identify what join isn’t finding a match or where bad data is throwing things into chaos. Get familiar with how joins actually work, even if you have to manually walk through the logic of a large stored procedure’s tree of joins. It’s boring and time-consuming but absolutely necessary.

Take the time to master the core skills that will make you a successful SQL Programmer and avoid queries that run for five hours!