Microsoft AI CEO Mustafa Suleyman has shared his beliefs regarding the biggest responsibilities of his role as the company races to develop increasingly advanced artificial intelligence systems. He said that his focus extends beyond building powerful models to ensuring they are developed in a responsible way, along with benefiting the masses.
Suleyman said, ‘We are doing this to solve real concrete problems and do it in such a way that it remains grounded and controllable,” Suleyman wrote. “We are not building an ill-defined and ethereal superintelligence; we are building a practical technology explicitly designed only to serve humanity.’ This came from Microsoft month after Mark Zuckerberg’s Meta invested billions to hire talent for its Superintelligence department.
Moreover, Mustafa Suleyman also said, ‘Shaping our culture at Microsoft AI is one of the most important responsibilities I have. Keeping our team lean and talent dense is critical to our success. It’s something I’ve thought very carefully about over the years.’ He also said that Microsoft asks everyone in the team to sing up to eleven principles before joining the team. His eleven pointers were:
We’re an IC-first team. Management is a service, not the goal. We’re here to empower, unblock and accelerate the exceptional work of our world-class ICs.
User focus. We build our models for end users. Developing user empathy begins with us. We always strive to use our own models first so we can hill climb for our users.
Take ownership of execution. Report issues, provide logs for debugging. First, try to fix things yourself. And see it right through to completion.
Scientific rigour above all else. We set hypotheses, rigorously ablate, and make data-driven decisions.
Constantly think simply. Simple methods scale best. No recipe changes unless deeply justified.
Know your data. Data is our lifeblood. No data black boxes. Every person is responsible for every token they add to the model.
Know your evals. No narratives without numbers. Production evals and trust internal metrics over academic benchmarks.
Don’t celebrate results prematurely. Maintain healthy scepticism. Check for reward hacking. Never cherry-pick results.
Always document everything. Positive and negative results are equally critical. Label every plot and axis. Summarise hypotheses and conclusions. Don’t use jargon.
Be precise and use neutral language. Describe situations accurately without unnecessary emotional charge.
Retrospectives drive everything. The culture and process flywheel is critical to our hill-climbing machine. We constantly run Retros to iterate and improve.
