Showing posts with label ROI. Show all posts
Showing posts with label ROI. Show all posts

Friday, March 26, 2021

Entrepreneurship - Problem Statement

A problem is a bad thing, right? Not necessarily. If you're trying to get hired to do a project for someone or start up your own business to provide various products and services to people, you have a clear problem you are trying to address.

The biggest issue I see with problem statements is that they generally come across as solutions or tritely state that the lack of this specific solution is a problem. In theory, it is great to be positive and go right to what you recommend in order to make your communications as clear as possible, but if there's no established problem, then no one will be listening, no matter how polished the sales pitch.

You have to bring attention to the imbalance, tension, or pain that exists in order to be able to show that your recommended solution will counteract it.

The following is a list of questions to ask to help define the problem. Without knowing the answers to these questions, the attempted start-up business is doomed to fail.

  • Context - when does the problem occur?
  • Customers - who has the problem most often?
  • Problem - what is the root cause of the problem?
  • Emotional impact - how does the customer feel?
  • Quantifiable impact - what is the measurable impact (units)?
  • Alternatives - what do customers do now to fix the problem?
  • Alternative shortcomings - what are the disadvantages of the alternatives?


Look at each question and answer them honestly. Hopefully, an entrepreneur has a passion for their business, but sometimes that passion can create a blind spot, where it's difficult to be honest with how good the proposed new product/service is. Include some other people in the process who are willing to be honest in answering the above questions.

If you don't know when the problem occurs or who it occurs to, stop right there. Your target customer needs to be clear since they are the ones you hope will pay you to solve their problems. Knowing that there is a problem is one thing, but knowing what is causing it is something else. A more elegant solution will be to address the root of an issue rather than just the symptoms.

People are emotional. They're also logical. Sometimes one side of the psyche wins out. Sometimes the other one does. How much better is it if you can make both emotional and logical pleas?

If you see a problem, chances are someone else does, too. Sometimes problems are small enough that the big players in the market don't find it worth their time to address the niche. As you look at the current alternatives to solve people's problems, consider what both works well and poorly about those current solutions. You need to be able to find something you can do that they can't (or won't).

There are various ways of implementing a competitive solution to a problem. Sometimes the first person to think of an idea becomes known, and the first-mover advantage is enough to carry them in front of others who come later. But more importantly, it is important to implement a solution that is difficult for others to copy. Creating the solution is a topic for another day, but it does start with understanding other current solutions clearly in order to figure out what they are doing wrong so that you can suggest a better way.

Tuesday, January 1, 2008

Investing in Security

A recent article discussed several myths and realities related to investments in information security. IS investments are very complicated, since companies must provide the "confidentiality, integrity, and availability of information, while also assuring authenticity and non repudiation…." That is to say, data needs to be protected against unknown change and kept away from non-authorized persons, while at the same time assuring that those who have legitimate business with that data are allowed full access.

Because of the complicated nature of many businesses, CxOs rightfully demand some monetary justification for pumping money into security rather than other projects that also need funding. According to the authors of this article, the traditional accounting measure, ROI, does not completely capture the benefits and risks associated with Information Security, so other measures must be used to find a project's Return on Security Investments (ROSI).

The first myth dispelled in the article is that "the accounting concept of 'return on investment' is an appropriate concept for evaluating information security investments." The problem with ROI is that it is an historical accounting measure. The IRR, an economic measure of future asset values and discounted cash flows, is a truer measure.

The second myth is that "Maximizing the IRR on information security investments is an appropriate objective." That is, the highest IRR is not necessarily the best choice. The amount of investment that yields the greatest net benefit is the one that should be used. The IRR measures a percentage return, not an actual return, so the IRR is used to a point, but to determine the actual amount to invest, the proportion with the largest actual return should be used. I'm not so sure that I agree with this point, but of course none of my articles have been published in Strategic Finance yet. What it looks like to me is that if another project has a higher marginal IRR, it will have a higher present value than the IS project, so the alternative project should receive the additional funding. This may be implied, but the article seems to focus on comparing a project's IRR only to itself, not to alternative projects.

The third myth is that "IRR and NPV are ex post metrics for evaluating the actual performance of information security investments." IRR is used to anticipate the returns of a project. Going back to measure the actual return on a project once it has been completed is called "post-auditing." Because of the nature of security investments, the more successful a project turns out to be, the fewer security problems will be seen, and the harder it will be to measure how successful it was. So the most successful project will result in no one even thinking about the security plan.

The fourth myth is that "it's appropriate to invest in security activities up to the level where the investments equal the expected loss from security breaches." The probability of an event taking place must be factored in when determining the present value of those investments. So, with this final point, the authors tell us that optimal level of security investments must be found, not just the project's rate of return.

In their research, they have found that on average, a maximum of about one-third of the expected potential loss should be invested in preventing that loss. By investing more than this, the amount spent preventing a loss approaches the amount of the loss. By investing less than this, a firm leaves its systems completely open.


Gordon, L.A. & Loeb, M.P. (2002). Return on information security investments: Myths vs realities. Strategic Finance, 84(5).