Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
wioota
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
Quality vs. speed in software development: insights for CEOs
(hyprinnovation.io)
1 points
by
wioota
2y ago
|
0 comments
2.
▲
by
wioota
2y ago
Time management might seem like a prosaic topic, but for any CTO who aspires to be more strategic, it starts with being in control of one's time.
3.
▲
OKRs vs. KPIs: How CTOs Can Leverage Both for Lasting Improvement
(greatcto.me)
2 points
by
wioota
2y ago
|
0 comments
4.
▲
Seven unchallenged assumptions stunting your company's growth
(wioota.substack.com)
1 points
by
wioota
2y ago
|
0 comments
5.
▲
A game to foster safe conversations on responsibilities within teams
(wioota.substack.com)
2 points
by
wioota
2y ago
|
0 comments
6.
▲
by
wioota
2y ago
How some tool providers describe OKRs it can be over-engineered I agree. You need to adapt tonyour context. E.g. startups can use OKRs but should be very lean about it. OKRs aren't really a framework - there's not lots of things y
7.
▲
by
wioota
2y ago
There isn't really one way to do OKRs - you can read a dozen different descriptions and have a dozen variations. It's not a formal methodology but rather an approach that for a long time was passed around organically based on some
8.
▲
by
wioota
2y ago
If it's seen as chore it's doomed to fail. Where I have seen it work well are in competitive markets such as SAAS companies battling for market share. The maturity for using measurement for decision making is higher because to do
9.
▲
by
wioota
2y ago
Might be semantics as the changes I describe are fairly substantial compared to how many companies implement them. I did think of not calling it OKRs anymore at the time but the effort to rebrand it internally didn't seem worth the pay
10.
▲
by
wioota
2y ago
Bad leadership will make a meal of any approach to work, its true. OKRs are not easy - they take good leadership, discipline and a culture which is open to feedback and committed to learning and adapting to what it learns. I wouldn't
11.
▲
by
wioota
2y ago
Achievable and valuable definitely more valuable than hard. I do suggest it's healthy not to 100% know how you might achieve the goal over the period - its good to be open to options and look for evidence you are making progress. I thi
12.
▲
by
wioota
2y ago
100% agree. Lots of other things need to be in a good healthy state for OKRs to be useful. Some of these are cultural such as it being safe to give feedback and a propensity to act on what is learnt. The ability to capture and update the pe
13.
▲
Improving OKRs
(wioota.substack.com)
63 points
by
wioota
2y ago
|
49 comments
14.
▲
by
wioota
4y ago
When your expertise applies to the qualitative aspects of a product or service, it can be a challenge to articulate the importance of issues. Here's an approach that may help you.
15.
▲
Influencing tip for engineers: Help others see what you see
(wioota.substack.com)
3 points
by
wioota
4y ago
|
1 comments
16.
▲
by
wioota
4y ago
Wow, didn't even think to post this here. Pretty cool :) Happy to chat about this post here or in the comments on my publication, Focus on outcomes.
17.
▲
by
wioota
16y ago
NodeJS, github and the Cloud9ide (powered by ACE editor) is a pretty good ecosystem for this. You can run it on Joyent's no.de hosting or EC2 (or the many other NodeJS hosting services springing up).
18.
▲
by
wioota
20y ago
This was a great read and the patterns of growth and strategies they used hold true even for much less extreme scaling.