If anyone is interested in OKRs, the North Star Framework, and/or connecting everyday work to the big picture… I'm doing a free presentation and Q&A on using OKRs with the North Star Framework on Aug 26th.
However I have mixed feelings for point 4, I guess it depends what you're counting. And I guess depending on the company context, it may be useless or very important.
For example,
By doing X , the customer should achieve Y
Y is the problem being solved, X is the solution to solve the problem.
If I integrate feedback & rework, then the new is:
We know that by doing X, the customer didn't achieve Y, but we believe
that by achieving X'' , the customer should achieve Y.
Yes, the problem solved is the same. However the solution to get to that point is not.
X and X'' are similar, but different. Why should we count them as the same thing ?
However I have mixed feelings for point 4, I guess it depends what you're counting. And I guess depending on the company context, it may be useless or very important.
For example,
By doing X , the customer should achieve Y
Y is the problem being solved, X is the solution to solve the problem.
If I integrate feedback & rework, then the new is:
We know that by doing X, the customer didn't achieve Y, but we believe
that by achieving X'' , the customer should achieve Y.
Yes, the problem solved is the same. However the solution to get to that point is not.
X and X'' are similar, but different. Why should we count them as the same thing ?
Hello there, thanks for this!
However I have mixed feelings for point 4, I guess it depends what you're counting. And I guess depending on the company context, it may be useless or very important.
For example,
By doing X , the customer should achieve Y
Y is the problem being solved, X is the solution to solve the problem.
If I integrate feedback & rework, then the new is:
We know that by doing X, the customer didn't achieve Y, but we believe
that by achieving X'' , the customer should achieve Y.
Yes, the problem solved is the same. However the solution to get to that point is not.
X and X'' are similar, but different. Why should we count them as the same thing ?
Hello there, thanks for this!
However I have mixed feelings for point 4, I guess it depends what you're counting. And I guess depending on the company context, it may be useless or very important.
For example,
By doing X , the customer should achieve Y
Y is the problem being solved, X is the solution to solve the problem.
If I integrate feedback & rework, then the new is:
We know that by doing X, the customer didn't achieve Y, but we believe
that by achieving X'' , the customer should achieve Y.
Yes, the problem solved is the same. However the solution to get to that point is not.
X and X'' are similar, but different. Why should we count them as the same thing ?