There is a particular kind of silence that follows success.
The photographs have been taken. The certificates have been handed out. The project has received its prize. Professors congratulate the students. Families are proud. Perhaps a local publication writes a few paragraphs about what these young engineers have accomplished.
Then graduation arrives.
And suddenly, a question that almost nobody asked during the celebration becomes unavoidable:
What happens next?
That question stayed with us after a nearly two-hour discussion with Moroccan engineer Hamza Kaddouri.
What began as a friendly conversation about engineering education, talent and the experience of being a young graduate quickly became something more substantial. Hamza was not interested in criticizing his former university, diminishing the effort of his professors or presenting himself as the inventor of a revolutionary technology.
Quite the opposite.
He spoke with respect for the people who encouraged him.
He also spoke with the perspective that only time can provide.
More than a decade after completing one of the most important technical projects of his student years, he still wonders why so much effort, ambition and potential can disappear almost immediately after graduation.
His question is simple.
It is also difficult to answer.
A very young engineer asking what comes next
Hamza graduated from a private university in Agadir.
For him, that detail matters.
His experience reinforced something he believes strongly today: Moroccan engineering talent cannot be reduced to the reputation of a university, the prestige of a campus or the name written across a diploma.
Talent exists far beyond the institutions traditionally considered elite.
What matters is what young people are encouraged to do with it.
During our discussion, Hamza repeatedly returned to this idea.
Young engineers can be capable, ambitious and technically creative regardless of where they studied. The more important question is whether they are given the opportunity to demonstrate those abilities and, once they do, whether anyone is prepared to help them take the next step.
That second part is where his own experience becomes particularly interesting.
On 20 March 2012, Hamza and four of his colleagues began working on a project that would remain with them throughout a significant part of their university experience.
It was not simply an assignment.
It was not part of a standard examination.
It developed through university activities, with the encouragement of a professor who, according to Hamza, approached the project with considerable ambition.
That ambition influenced the students.
They began to believe that what they were building could become something serious.
The greenhouse
The idea was a smart greenhouse.
Hamza is the first to acknowledge that the concept itself was not new.
Automated greenhouses already existed. Monitoring temperature, humidity, irrigation and soil or water conditions was not an invention unique to their team.
Their objective was more specific.
They wanted to create a system that could allow a farmer to select a crop and then use sensing, control and automation to help maintain conditions appropriate for that crop.
The system would consider parameters such as irrigation, temperature, humidity and pH, among others, and use automation to support better growing conditions.
In today's language, many would describe such a system using terms such as smart agriculture, precision agriculture or intelligent environmental control.
But the terminology is less important than what five young students actually attempted to do.
They wanted to integrate several technical functions into one working physical system.
And they did not stop at a presentation.
They built it.
Approximately $6,000 of their own money
This part of Hamza's story deserves attention.
The students were young.
They were still studying.
Yet, according to Hamza, the team collectively invested approximately $6,000 of their own money into the project.
For students, particularly at that stage of their lives, this was not a trivial contribution.
It represented belief.
It represented risk.
And it represented the kind of commitment that universities often say they want to encourage in young engineers.
Over time, the team produced a functional proof of concept measuring approximately four metres by two metres by three metres.
This was no tabletop demonstration.
It was large enough to become a real engineering object—something that had to be assembled, wired, controlled, tested, corrected and made to function as an integrated system.
Anyone who has built physical systems knows how different that is from describing them.
On paper, components cooperate perfectly.
In reality, sensors behave unexpectedly. Connections fail. Measurements drift. Mechanical constraints appear. Components interfere with one another. Costs increase. Parts arrive late. Software behaves differently once connected to hardware.
Engineering begins when the assumptions start meeting reality.
That experience alone has value.
They won
The project eventually received first prize.
It was also covered in a local university-related publication, which Hamza recalls as issue No. 104, dated 27 November 2013, under the reference Dépôt 64/94.
For a group of young students, these were important moments.
Their work had been recognized.
The long hours had produced something visible.
Their investment had resulted in a functioning system.
Their professor's confidence in the project appeared justified.
From the outside, this is where the story looks complete.
A student team builds an ambitious prototype.
The prototype works.
They receive recognition.
They win an award.
The university celebrates.
The students graduate.
Success.
But Hamza's concern begins exactly where that version of the story ends.
After the applause
What happened to the project?
That was the question he asked us.
Not angrily.
Not accusingly.
With respect.
But also with the frustration of someone who had personally experienced what happens when an academic project reaches the edge of the institution that helped create it.
Once the students graduated, the project effectively ended.
There was no meaningful continuation.
No structured follow-up.
No obvious pathway toward further development.
No transition from student prototype to a longer-term technical program.
Years of effort suddenly belonged to the past.
And Hamza's question was not merely, Why didn't our greenhouse become a company?
That would be too simplistic.
Most prototypes do not become companies.
Most ideas require significant revision.
Some should be abandoned.
Others prove technically possible but commercially irrelevant.
A university prototype is not automatically a product, and winning a student competition does not prove market viability.
Hamza understands that.
The more important question is why there was apparently no mechanism capable of determining what the project might have become.
What if the answer had been no?
This distinction matters.
Suppose the greenhouse had received another six months of technical evaluation.
Suppose agricultural specialists had reviewed it.
Suppose the design had been tested with farmers.
Suppose engineers had examined its reliability, cost, maintainability and manufacturability.
Suppose the conclusion had been: This project should not continue.
That would still have been an outcome.
There would have been lessons.
The students would have understood why.
The university would have accumulated technical knowledge.
The next student team could have begun from a more advanced point.
Instead, what troubles Hamza is the possibility that the project was neither developed nor rejected.
It simply stopped.
There is a profound difference between failure and disappearance.
Failure can teach.
Disappearance teaches almost nothing.
The problem of visibility
As our discussion continued, Hamza widened the subject beyond his own experience.
He spoke about visibility.
This affects students, young engineers, independent developers and freelancers throughout Morocco.
A talented engineer can build something impressive and still remain almost invisible to the people capable of financing, testing, manufacturing or deploying it.
Technical ability does not automatically create access.
A student may know how to design a control system but have no idea how to reach an agricultural company.
A freelancer may build a working prototype without knowing how to approach an investor.
A young graduate may be technically capable of improving an existing industrial process while having no connection to the industry that needs that improvement.
This is where the ecosystem around innovation becomes as important as innovation itself.
The challenge is not simply producing talented engineers.
Morocco already produces them.
The challenge is making sure capable people do not remain disconnected from opportunity.
Financing is part of the equation
Hamza also spoke about financing.
His own team financed a significant part of their project personally.
That demonstrated commitment.
But it also exposes a structural limitation.
How many talented students can afford to do the same?
How many potentially useful ideas disappear before the first prototype because the students involved simply cannot finance the components?
And what happens when a successful prototype requires ten times more money to reach the next level?
Student enthusiasm can finance a few sensors.
It cannot finance an industrialization program.
Personal savings can build a proof of concept.
They cannot replace an innovation ecosystem.
This is where universities, industry, public institutions, investors and technical organizations have to meet.
Not every project deserves money.
But promising projects deserve evaluation.
That distinction should guide any serious innovation strategy.
Compatible with a broader national ambition
Hamza also views the project through the context of Morocco's long-standing ambition to modernize agriculture and increase the use of technology within the sector.
That does not mean his university greenhouse should be presented as a missing national breakthrough.
It should not.
The technology was not unique, and a student prototype should never be exaggerated simply because it fits a larger national objective.
But the project demonstrated something arguably more important.
Young Moroccan engineers were already thinking about how automation, sensing, environmental monitoring and control systems could be applied to agriculture.
They were willing to build.
They were willing to spend their own money.
They were willing to learn.
They were willing to take risks.
That capacity is valuable regardless of whether one individual greenhouse survived.
The question is how many similar projects have existed since then.
And how many disappeared the same way.
Universities cannot carry the entire burden
It would be easy to turn this discussion into criticism of universities.
That would miss the point.
Hamza's own story contains evidence of what a university can do well.
A professor encouraged students to aim higher.
An institution created space for extracurricular technical work.
Students were given an opportunity to build.
Their effort was recognized.
The project competed and won.
Those are not failures.
The weakness appears in the transition between stages.
Universities are educational institutions. They cannot be expected to transform every student project into a startup, maintain every prototype indefinitely or finance every graduating team.
Industry cannot fund every idea either.
Government programs cannot save every project.
Investors certainly should not finance everything that wins a student prize.
What is missing is not unlimited support.
What is needed is a filtering and continuation mechanism.
A way to ask: Does this project deserve another stage? Does it need research support? Does it need an industrial partner? Does it need a field test? Does it need intellectual-property advice? Does it need business mentoring? Or has it already reached the end of its useful life?
Any of those answers is better than silence.
The bridge between education and industry
One of the strongest conclusions from our conversation with Hamza is that Morocco's challenge is not solely an educational one.
It is a continuity problem.
Universities generate projects.
Competitions identify talent.
Young engineers demonstrate ability.
Then industry waits somewhere else.
Between those worlds there is often a gap.
The student does not know the manufacturer.
The manufacturer does not know the student.
The investor does not understand the technology.
The engineer does not understand financing.
The agricultural operator does not know that a university laboratory has already built something relevant to his problem.
Everybody exists.
But they do not necessarily meet.
That is the bridge that matters.
Talent is not the same as pedigree
There was another message in Hamza's story that deserves to stand on its own.
He was very young when this happened.
He came from a private university in Agadir.
Yet his team built something substantial enough to receive recognition and win a competition.
For him, this experience helped confirm a belief he still carries today: Talent is not owned by famous universities.
A prestigious institution can provide extraordinary resources, networks and opportunities.
Those things matter.
But the absence of a famous name on a diploma does not imply the absence of engineering ability.
Morocco cannot afford to search for talent only in obvious places.
Some of the country's strongest future engineers may be studying today in institutions that receive little attention.
Others may be learning independently.
Some may be building projects in garages.
Some may be freelancers.
Some may already have graduated and entered completely unrelated jobs because they never found the bridge between their technical ability and an opportunity to use it.
An innovation ecosystem that only recognizes pedigree will inevitably overlook talent.
There is also a documentation problem
Another issue emerged indirectly from the conversation.
Today, more than a decade later, Hamza does not have the full technical documentation, blueprints or detailed project records available to reconstruct the greenhouse for us.
That is understandable.
Students graduate.
Computers are replaced.
Files disappear.
Laboratories change.
Teams separate.
But this raises an important institutional question.
Where is the memory of student innovation stored?
If a university supports hundreds of technical projects over twenty years, those projects represent a considerable body of practical knowledge.
Design decisions.
Failures.
Source code.
Mechanical drawings.
Test results.
Cost estimates.
Experimental data.
Lessons.
Even projects that never become products can contribute to future engineering work.
But only if the knowledge survives the students who created it.
A project archive should not be a cemetery.
It should be a foundation.
What recognition should mean
Awards have value.
Hamza remembers his team's first prize.
He remembers the publication.
He remembers the professor who believed in the project.
Those moments clearly mattered.
But perhaps recognition needs a second definition.
The first form of recognition says: You did good work.
The second asks: What do we do with this work now?
That is a much harder question.
It requires institutions to distinguish between celebration and development.
A trophy is easy.
A continuation strategy is difficult.
Continuation means evaluation.
Evaluation sometimes means criticism.
It means deciding that a beloved student project may not be viable.
It means connecting engineers with people outside academia.
It means allowing ideas to encounter real customers, real environments, real regulations and real economic constraints.
That is how engineering grows up.
The project may be gone. The question remains.
Hamza's greenhouse belongs to another period of his life.
He is not asking us to revive it.
He is not claiming that Morocco lost a billion-dollar company because five students were not given another grant.
That would distort his story.
His question is broader and more useful than that.
What happens to promising student work when the students leave?
What happens to the prototype after the exhibition?
What happens to the engineering after the newspaper article?
What happens to the team after the graduation photographs?
What happens to everything that was learned?
If the answer is simply, nothing, then something important is being lost.
Not every project.
Not every prototype.
Not every idea.
But potentially, some of them.
And perhaps even more importantly, the people behind them.
What young engineers need after the trophy
Our conversation with Hamza Kaddouri ultimately left us thinking less about one greenhouse and more about what a healthy engineering ecosystem should look like.
Young engineers need universities that challenge them.
They need professors who believe ambitious projects are possible.
They need laboratories.
They need competitions.
They need recognition.
But after that, the strongest among those projects need another door.
A door toward industry.
A door toward testing.
A door toward financing.
A door toward research.
A door toward entrepreneurship.
Sometimes even a door toward a professional technical review that tells the team, respectfully and clearly, that the project should end.
Because an engineering project does not have to become a company to have value.
It has to produce knowledge.
And that knowledge should lead somewhere.
Hamza and four colleagues began their project on 20 March 2012.
They invested their own money.
They built a functioning greenhouse.
They received first prize.
They saw their work published.
They graduated.
More than a decade later, what remains most clearly is not the machine.
It is the question.
After the trophies, after the publication, after the congratulations—what happens after the applause?
After the trophies, after the publication, after the congratulations—what happens after the applause?